Skip to content

[Snyk] Security upgrade aws-amplify from 4.3.33 to 5.3.15#629

Open
macpro-snyk-service-account wants to merge 1 commit intomasterfrom
snyk-fix-32c0e2a1cf3abc85a25b2090de1991d4
Open

[Snyk] Security upgrade aws-amplify from 4.3.33 to 5.3.15#629
macpro-snyk-service-account wants to merge 1 commit intomasterfrom
snyk-fix-32c0e2a1cf3abc85a25b2090de1991d4

Conversation

@macpro-snyk-service-account
Copy link
Copy Markdown
Collaborator

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

  • services/ui-src/package.json
  • services/ui-src/yarn.lock

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Allocation of Resources Without Limits or Throttling
SNYK-JS-AXIOS-15930944
  157  

Breaking Change Risk

Merge Risk: High

Notice: This assessment is enhanced by AI.


Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Allocation of Resources Without Limits or Throttling

…ce vulnerabilities

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-AXIOS-15930944
@macpro-snyk-service-account
Copy link
Copy Markdown
Collaborator Author

Merge Risk: High

The upgrade from aws-amplify v4 to v5 is a major version change that includes significant breaking changes requiring code modifications.

Key Breaking Changes:

  • Removal of Default Exports: All default exports have been removed. You must refactor your import statements to use named imports.

    • Before: import Auth from '@aws-amplify/auth';
    • After: import { Auth } from '@aws-amplify/auth';
    • This change applies to most Amplify categories, including api, analytics, cache, datastore, and geo.
  • Storage API Changes: The Storage.list method has been updated. The maxKeys parameter is now pageSize, and the method returns a different object structure.

  • Legacy UI Packages Deprecated: Older UI component libraries like @aws-amplify/ui-react@<=1.x, @aws-amplify/ui-angular@<=1.x, and aws-amplify-react are deprecated. If you use these, you will need to migrate to the newer @aws-amplify/ui-* packages.

Recommendation:
Due to the removal of default exports, this upgrade will require a codebase-wide refactoring of all aws-amplify import statements. This is a high-impact change that must be addressed before the application will run correctly.

Source: Announcing AWS Amplify JavaScript library version 5

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

@macpro-snyk-service-account
Copy link
Copy Markdown
Collaborator Author

macpro-snyk-service-account commented Apr 9, 2026

Snyk checks have passed. No issues have been found so far.

Status Scan Engine Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues
Licenses 0 0 0 0 0 issues
Code Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

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.

2 participants