chore: skipped aws dynamodb currency updates #2323
Merged
Conversation
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
aryamohanan
commented
Feb 4, 2026
| }); | ||
|
|
||
| execSync("git add '*package.json' package-lock.json", { cwd }); | ||
| execSync(`git commit -m "build: bumped ${packagesToUpdate.join(', ')} to ${targetVersion}"`, { cwd }); |
Contributor
Author
There was a problem hiding this comment.
discussed offline and decided to skip the updates for now, this will be fixed #2306 is merged
abhilash-sivan
approved these changes
Feb 4, 2026
|
aryamohanan
changed the title
aryamohanan
changed the title
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.
@aws-sdk/client-dynamodb and @aws-sdk/lib-dynamodb were both listed in currencies.json and were being updated independently. However, @aws-sdk/client-dynamodb is a peer dependency of @aws-sdk/lib-dynamodb.
Because of this, when the currency update job ran, it often failed with an npm peer dependency conflict. In practice, these two packages must be updated simultaneously to the same version.
Currently, updates for these dependencies are being skipped to avoid npm peer dependency conflicts.
reference https://jsw.ibm.com/browse/INSTA-74688