Skip to content

chore: Upgrade to Go 1.21, several AWS dependencies#558

Merged
bhavanki merged 2 commits intomasterfrom
aws-dep-upgrades
Aug 19, 2024
Merged

chore: Upgrade to Go 1.21, several AWS dependencies#558
bhavanki merged 2 commits intomasterfrom
aws-dep-upgrades

Conversation

@bhavanki
Copy link
Contributor

@bhavanki bhavanki commented Aug 19, 2024

I filed this as an alternative to five other dependabot PRs, and to investigate why they were failing. Once this one is merged, those other PRs will become obsolete.

The root problem discovered here is that the AWS SDK just increased its minimum Go version to 1.21. Chamber may do the same, since it only supports the most recent two Go versions. Although 1.21 is now the third most recent, we'll leave it in since it can at least build.

#559 also groups future aws-sdk-go-v2 upgrades into single PRs, for easier review and more efficient use of GitHub resources.

@bhavanki bhavanki requested a review from a team as a code owner August 19, 2024 17:38
@bhavanki
Copy link
Contributor Author

Ah, the AWS SDK now requires Go 1.21. https://github.com/aws/aws-sdk-go-v2/releases/tag/release-2024-08-15

@bhavanki bhavanki changed the title chore: Upgrade several AWS dependencies chore: Upgrade to Go 1.21, several AWS dependencies Aug 19, 2024
alecjacobs5401
alecjacobs5401 previously approved these changes Aug 19, 2024
go.mod Outdated
go 1.20
go 1.21

toolchain go1.21.6
Copy link
Contributor

@alecjacobs5401 alecjacobs5401 Aug 19, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

open question on this - would we not want this to be the latest go version we are building and running with?

In our Dockerfile, we're using 1.22 still

FROM golang:1.22.6-alpine AS build

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Turns out we don't need the toolchain line. go mod tidy added it, I suppose based on what I have locally, but go get toolchain@none(ref) removed it, and everything still seems OK.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Oh, as for the Dockerfile, dependabot is already on it: https://github.com/segmentio/chamber/pull/557/files

@bhavanki bhavanki merged commit 22441a2 into master Aug 19, 2024
@bhavanki bhavanki deleted the aws-dep-upgrades branch August 19, 2024 20:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants