Repository navigation
chore: bump AWS CLI pin 2.35.4 → 2.36.11 - #28
Merged
Merged
Conversation
Routine upstream bump of AWS_CLI_VER in install-tools.sh. No paired
checksum change is needed: the AWS CLI supply-chain gate verifies the
detached .sig against AWS's public-key fingerprint (AWS_CLI_PGP_FPR),
which is stable across releases, rather than a per-release digest.
Confirmed both arch bundles and their signatures publish at the
versioned download path before moving the pin:
awscli-exe-linux-x86_64-2.36.11.zip{,.sig} -> 200
awscli-exe-linux-aarch64-2.36.11.zip{,.sig} -> 200
2.36.12 does not exist yet (404), so 2.36.11 is current latest.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
1 participant
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.
What
Bumps
AWS_CLI_VERin.devcontainer/install-tools.shfrom2.35.4to2.36.11(latest published AWS CLI v2), plus aCHANGELOG.mdentry under[Unreleased].Why no paired checksum change
The pinned-version block says "bump deliberately; update the paired checksum at the same time" — that applies to yq/lazygit, which pin a per-release SHA-256. The AWS CLI gate is different: it verifies the release's detached PGP signature against
AWS_CLI_PGP_FPR(FB5DB77F…4672475C), AWS's public-key fingerprint, which is stable across releases. So the integrity gate carries over to the new version unchanged.Verification
Confirmed both arch bundles and their signatures publish at the versioned download path before moving the pin:
awscli-exe-linux-x86_64-2.36.11.zip+.sigawscli-exe-linux-aarch64-2.36.11.zip+.sig…-2.36.12.…Local
shellcheckanddocker compose config -qpass;hadolint/yamllintaren't installed on the dev host, and neither the Dockerfile nor any YAML changed here — CI covers both.Operational note
The CLI installs to
/usr/local/aws-cli, which is not a named volume, so this lands only on a container recreate (make up/make rebuild), not adocker stop/start. Credentials are unaffected —AWS_CONFIG_FILE/AWS_SHARED_CREDENTIALS_FILEpoint into theclaude-configvolume.🤖 Generated with Claude Code