Skip to content

backend/s3: bump github.com/hashicorp/aws-sdk-go-base/v2#38047

Merged
jar-b merged 1 commit intomainfrom
s3/aws-sdk-go-base-upgrade
Jan 20, 2026
Merged

backend/s3: bump github.com/hashicorp/aws-sdk-go-base/v2#38047
jar-b merged 1 commit intomainfrom
s3/aws-sdk-go-base-upgrade

Conversation

@jar-b
Copy link
Member

@jar-b jar-b commented Jan 8, 2026

Incrementing the aws-sdk-go-base dependecy will also pull in the latest version of the AWS SDK for Go V2, which includes support for the newly launched aws login authentication method.

% TF_ACC=1 go test -count=1 ./...
ok      github.com/hashicorp/terraform/internal/backend/remote-state/s3 202.079s

Closes #37976

Target Release

1.15.x

CHANGELOG entry

  • This change is user-facing and I added a changelog entry.
  • This change is not user-facing.

Incrementing the `aws-sdk-go-base` dependecy will also pull in the latest version of the AWS SDK for Go V2, which includes support for the newly launched `aws login` authentication method.
@jar-b jar-b merged commit 35e81db into main Jan 20, 2026
15 checks passed
@jar-b jar-b deleted the s3/aws-sdk-go-base-upgrade branch January 20, 2026 16:00
@gluehbirnenkopf
Copy link

gluehbirnenkopf commented Jan 21, 2026

@jar-b - I assumed it would be included in the next TF patch release v1.14.4, but saw in this PR it will be 1.15.x.

is there already an ETA for the release including this bugfix/update?

@jar-b
Copy link
Member Author

jar-b commented Jan 21, 2026

Correct, Terraform core typically does not include dependency updates in patch releases to avoid any breaking behavioral changes, so we've targeted 1.15 here.

I don't have specifics on anticipated release dates as I'm not a member of the core team. The typical cadence is ~3-4 months between minor versions.

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.

S3 Backend: Support authentication via aws login

3 participants