docs: update all docs and examples for v1.0.1 release#746
Merged
Conversation
Bump the Docker image tag from 1.0.0 to 1.0.1 and the Lambda layer version from 27 to 28 across the README, user guide, Dockerfiles, SAM templates, and example READMEs, and add the v1.0.1 CHANGELOG section, mirroring the 1.0.0 release update (aws#689). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
JamBalaya56562
force-pushed
the
docs-update-v1.0.1
branch
from
70789e8 to
2dd1dbd
Compare
bnusunny
approved these changes
Jun 1, 2026
Contributor
bnusunny
left a comment
bnusunny
left a comment
There was a problem hiding this comment.
Thanks for the update. I will automate this update via the release pipeline.
JamBalaya56562
added a commit
to JamBalaya56562/aws-lambda-web-adapter
that referenced
this pull request
Jun 2, 2026
Automate the manual version-string sweep that PR aws#746 did by hand, per the maintainer's note on that PR ("I will automate this update via the release pipeline"). Two hard-coded references across docs/examples are kept in sync: - Docker image tag public.ecr.aws/awsguru/aws-lambda-adapter:<X.Y.Z> (= the crate semver) - Lambda layer version LambdaAdapterLayer{X86,Arm64}:<N> (an integer AWS assigns at publish time) How: - scripts/update-versions.sh <image_version> <layer_version>: a reusable, idempotent, anchored updater (skips CHANGELOG.md history and the obsolete commented example ARN, account 753240598076). Runnable by a human too. - release-plz.yml: after release-plz opens/updates the Release PR, an inject step predicts the next layer version (current + 1) and the new image tag and amends them into the same release commit. The +1 prediction is reliable because the SAM layer's Description embeds the crate version, so every release publishes exactly one new immutable layer version. - release.yaml: a post-deploy verify-layer-versions job reads the ACTUAL published layer version and opens a self-healing correction PR if the prediction was ever wrong. (Requires lambda:ListLayerVersions on the prod pipeline role; the prediction stands on its own without it.) Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
JamBalaya56562
added a commit
to JamBalaya56562/aws-lambda-web-adapter
that referenced
this pull request
Jun 2, 2026
Automate the manual version-string sweep that PR aws#746 did by hand, per the maintainer's note on that PR ("I will automate this update via the release pipeline"). Two hard-coded references across docs/examples are kept in sync: - Docker image tag public.ecr.aws/awsguru/aws-lambda-adapter:<X.Y.Z> (= the crate semver) - Lambda layer version LambdaAdapterLayer{X86,Arm64}:<N> (an integer AWS assigns at publish time) How: - scripts/update-versions.sh <image_version> <layer_version>: a reusable, idempotent, anchored updater (skips CHANGELOG.md history and the obsolete commented example ARN, account 753240598076). Runnable by a human too. - release-plz.yml: after release-plz opens/updates the Release PR, an inject step predicts the next layer version (current + 1) and the new image tag and amends them into the same release commit. The +1 prediction is reliable because the SAM layer's Description embeds the crate version, so every release publishes exactly one new immutable layer version. - release.yaml: a post-deploy verify-layer-versions job reads the ACTUAL published layer version and opens a self-healing correction PR if the prediction was ever wrong. (Requires lambda:ListLayerVersions on the prod pipeline role; the prediction stands on its own without it.) Co-Authored-By: Claude Opus 4.8 <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
2 participants
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.
Description
Updates documentation and examples for the v1.0.1 release, mirroring the 1.0.0 docs update in #689.
public.ecr.aws/awsguru/aws-lambda-adapter:1.0.0→:1.0.1(README, user guide, Dockerfiles, example READMEs,examples.yamlCI workflow)LambdaAdapterLayer{X86,Arm64}:27→:28(README, user guide, SAM templates, example READMEs, CDK app)Verification
The commercial layer version
:28was confirmed against the actualv1.0.1release run (sam deployCloudFormation outputs), e.g.arn:aws:lambda:us-east-1:753240598075:layer:LambdaAdapterLayerX86:28(verified consistent across the sampled commercial regions for both x86_64 and arm64).The Docker tag is derived directly from
CARGO_PKG_VERSIONin the release workflow, so1.0.1is exact.Type of change
🤖 Generated with Claude Code