Repository navigation
chore: upgrade RIE to 1.37 - #9209
Merged
Merged
Conversation
Picks up v1.35 (Lambda Metadata Service support), v1.36 and v1.37. The Go toolchain embedded in the binaries moves from 1.25.8 to 1.26.7.
roger-zhangg
enabled auto-merge
August 31, 2026 22:16
vicheey
approved these changes
Aug 31, 2026
ckawl
approved these changes
Sep 1, 2026
roger-zhangg
added this pull request to the merge queue
Sep 1, 2026
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.
Syncs the vendored RIE binaries to v1.37.
Which issue(s) does this change fix?
N/A
Why is this change necessary?
samcli/local/rapid/vendors the RIE binaries thatsam local invoke/start-api/start-lambdamount into the runtime container. They were last synced at 1.34 (#8827), so this picks up three releases:Confirmed from the binaries themselves rather than the release notes alone: the embedded Go toolchain moves from go1.25.8 to go1.26.7 (
go version -m), and 1.25.8 matches what #8827 recorded for 1.34.How does it address the issue?
Replaces
aws-lambda-rie-x86_64andaws-lambda-rie-arm64with the v1.37 release assets. No other changes β there is no version constant in the repo, the binaries are the only artifact.What side effects does this change have?
None expected; this is the same binary swap as #8827 and #8561.
Verified before committing:
fileconfirms each is the right architecture (x86-64 and ARM aarch64), so the two are not transposed.go version -mreports the module pathgithub.com/aws/aws-lambda-runtime-interface-emulator/cmd/aws-lambda-riefor both.100755for both, so the missing exec-permission follow-up needed in chore(deps): update RIE to 1.31Β #8561 does not recur.make prpasses (9401 unit tests, 94.09% coverage).I could not run
sam local invokelocally as Docker was unavailable, so the runtime exercise of these binaries is left to the integration tests in CI.Mandatory Checklist
PRs will only be reviewed after checklist is complete
make prpassesmake update-reproducible-reqsif dependencies were changedBy submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.