Skip to content

feat: use caret range for aws-sdk deps #14425

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

monholm
Copy link
Contributor

@monholm monholm commented Jun 10, 2025

Description of changes

This pull request migrates all aws-sdk dependencies to use caret version range.

The aws-sdk is a rather large dependency, and most of it's packages are highly entangled and depend on fixed versions, i.e. adding a single package as a dependency installs quite a few other packages from aws-sdk.

As an example, installing @aws-sdk/client-firehose (a dep of @aws-amplify/analytics) adds 22 different aws-sdk packages.

This becomes quite annoying if depending on aws-sdk myself, as it will result in a lot of duplicate packages with varying versions, or alternatively forcing me to use the same (old) version that aws-amplify depends on.

The aws-sdk is strict on not introducing breaking changes, so I see no reasing enforcing a specific version :)

Checklist

  • PR description included
  • yarn test passes
  • Unit Tests are changed or added
  • Relevant documentation is changed or added (and PR referenced)

Checklist for repo maintainers

  • Verify E2E tests for existing workflows are working as expected or add E2E tests for newly added workflows
  • New source file paths included in this PR have been added to CODEOWNERS, if appropriate

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@monholm monholm requested review from a team as code owners June 10, 2025 18:13
@monholm monholm changed the title feat: use caret range for @aws-sdk deps feat: use caret range for aws-sdk deps Jun 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant