Repository navigation
feat(clients): enable 2026 new retry behavior by default - #8413
Merged
Merged
Conversation
4 of 8 tasks
Alan4506
force-pushed
the
retries-2026-default
branch
from
November 9, 2026 21:00
5c92f9e to
870b58c
Compare
Alan4506
force-pushed
the
retries-2026-default
branch
from
November 10, 2026 15:33
01aa610 to
d0967dc
Compare
Alan4506
marked this pull request as ready for review
November 10, 2026 15:41
ubaskota
approved these changes
Nov 10, 2026
kuhe
approved these changes
Nov 10, 2026
smilkuri
approved these changes
Nov 10, 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.
Summary
Removes the aws-sdk-js-v3 side of the
AWS_NEW_RETRIES_2026opt-in added in #7922.@smithy/core3.40.0 enables the 2026 retry behavior by default and makesRetry.v2026a readonlytrue, so the remaining opt-in code is dead code.The
setFeature.tsenv var read, theRetry.v2026toggling in the retry-customization and SQS long-poll specs, and the DynamoDB snapshot change (max=3tomax=4) were already removed in #8415 because they did not compile or pass against@smithy/core3.40.0. This PR removes what is left.Changes
AddRetryCustomizations.java: the DynamoDB and DynamoDB Streams defaults (4 attempts, 25 ms base delay) are emitted directly instead of behindRetry.v2026.client-dynamodbandclient-dynamodb-streamsregenerated; theRetryimport and theRetry.v2026 ? … : …expressions are gone. No snapshot changes.retry.integ.spec.jsand itstest:temp:temp:retryscript removed (they asserted that the env vars set the flag); the browser test bundle no longer re-exportsRetry.Testing
generate-clientsfordynamodbanddynamodb-streamson top of chore(codegen): sync for 2026 retry defaults #8415: no further diff; snapshot suite passes.Related
Checklist
*.integ.spec.ts) or E2E tests.@public,@internaltags and enabled doc generation on the package. Remember that access level annotations go below the description, not above.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.