Skip to content

[Snyk] Security upgrade aws-amplify from 4.3.33 to 5.3.4#626

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

[Snyk] Security upgrade aws-amplify from 4.3.33 to 5.3.4#626
macpro-snyk-service-account wants to merge 1 commit intomasterfrom
snyk-fix-ff5f00ec7a20c389c930d9bcf3406faf

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
medium severity Buffer Overflow
SNYK-JS-FASTXMLPARSER-15353391
  50  

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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.

…ce vulnerabilities

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

Merge Risk: High

This major version upgrade from aws-amplify v4 to v5 introduces significant breaking changes that require code modifications.

Key Breaking Changes:

  • Named Imports Required: Default exports have been removed across many Amplify packages. You must update your import statements from import Auth from '@aws-amplify/auth' to import { Auth } from '@aws-amplify/auth'. This applies to categories like analytics, api, cache, datastore, and storage.
  • API Method Signature Changes:
    • Storage: The Storage.list method now uses a pageSize parameter instead of maxKeys, and its return value is an object with pagination information.
    • Analytics: The Analytics.record method no longer accepts a string as its first parameter.
  • Deprecated UI Packages: Legacy UI packages (e.g., @aws-amplify/ui-react@<=1.x, @aws-amplify/ui-angular@<=1.x) are deprecated and users are encouraged to migrate to the newer UI packages.

Recommendation:
Developers must review their code to update all aws-amplify imports to use named imports. Usages of Storage.list and Analytics.record must be updated to match the new API signatures. If you are using the legacy UI packages, a migration plan to the new UI components is required.

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 Feb 27, 2026

Snyk checks have failed. 3 issues have been found so far.

Status Scanner Critical High Medium Low Total (3)
Open Source Security 0 3 0 0 3 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