Repository navigation
chore(deps,terraform): bump hashicorp/aws from 6.46.0 to 6.63.0 in /infrastructure/terraform - #253
Closed
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [hashicorp/aws](https://github.com/hashicorp/terraform-provider-aws) from 6.46.0 to 6.63.0. - [Release notes](https://github.com/hashicorp/terraform-provider-aws/releases) - [Changelog](https://github.com/hashicorp/terraform-provider-aws/blob/main/CHANGELOG.md) - [Commits](hashicorp/terraform-provider-aws@v6.46.0...v6.63.0) --- updated-dependencies: - dependency-name: hashicorp/aws dependency-version: 6.63.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
Contributor
Author
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
DORA Metrics
|
brownjuly2003-code
pushed a commit
that referenced
this pull request
Sep 8, 2026
…exact pin Dependabot's #253 proposed the same 6.46.0 -> 6.63.0 bump and could not be merged: its updater rewrote `version = "= 6.46.0"` to `version = "6.63.0"`, dropping the operator that makes the pin exact, and test_terraform_state_contract.py failed it (run 34213669766). It also locks only linux_amd64, while the terraform-validate provider-lock step diffs all three platforms. Done by hand instead, keeping both properties. AWS_PROVIDER_VERSION in the contract test moves with main.tf, so the pin, the lock and the assertion stay one fact in three places. The lock was rebuilt one platform at a time. `terraform providers lock` refuses to move a version the lock already records ("must use terraform init -upgrade to allow selection of new versions"), so the sequence is `init -backend=false -upgrade` first -- which records only the host platform -- and then the lock command. Passing three platforms at once means three ~250 MB fetches in one process, which did not survive this link; the hashes accumulate across invocations, so linux_amd64 and darwin_arm64 were added separately and the file ends up byte-identical to what CI's single three-platform command produces. Verified: `terraform validate` Success against 6.63.0 (17 minors is enough to remove an attribute; it does not), lock carries three h1: hashes plus the registry zh: set, test_terraform_state_contract.py 14 passed. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_015HsJh4f7Lqv3XmkCPSA1uF
Contributor
Author
|
Looks like hashicorp/aws is up-to-date now, so this is no longer needed. |
dependabot
Bot
deleted the
dependabot/terraform/infrastructure/terraform/hashicorp/aws-6.63.0
branch
September 8, 2026 18:57
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps hashicorp/aws from 6.46.0 to 6.63.0.
Release notes
Sourced from hashicorp/aws's releases.
... (truncated)
Changelog
Sourced from hashicorp/aws's changelog.
... (truncated)
Commits
07c0e84Merge pull request #49809 from hashicorp/td-crypto-depse0c0060chore: updatev6.63.0release date (#49827)1dd080aMerge pull request #49817 from hashicorp/ci-smoke-test-failure-output3d1b9edPreventserrexitfrom terminating script4c7d08aMerge pull request #49803 from hashicorp/ci-smoke-test-failure-output334a9d4deps: bumpgolang.org/x/cryptoin.ci/providerlint32c5987deps: bumpgolang.org/x/cryptoin.ci/toolsec70c73deps: bumpgolang.org/x/cryptoe47230echore:v6.63.0release prep (#49796)1f9c26bMoves-jsonflag out of build config and into scriptDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)