Repository navigation
chore(deps): bump the e2e module's lambda and s3 clients - #1276
Merged
Merged
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
scttfrdmn
added a commit
that referenced
this pull request
Oct 1, 2026
Takes Dependabot's proposal (#1294) with a changelog line attached, which CLAUDE.md asks of every PR and which Dependabot cannot write. The root module carries no AWS SDK dependency, so as with #1276 and unlike #1269 this needs no matching re-tidy of the other module; test/e2e was re-tidied anyway to confirm that, and go mod tidy produced no further change. Supersedes #1294.
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.
Dependabot's
test/e2ebump (#1270), taken by hand so it carries the changelog line CLAUDE.mdasks of every PR.
Unlike #1267 this one needs no matching root-module half: the two clients that moved
(
aws-sdk-go-v2/service/lambda1.108.0→1.109.0,service/s31.113.1→1.113.2) are E2E-onlyrequirements, and re-tidying
test/e2econfirmed the root module is untouched — 0 files. That isthe difference from #1269, where a root bump left the E2E module's indirect requires stale and the
E2E Testsjob failed on the untidy module.Supersedes #1270, which is closed in favour of this.