Skip to content

[Snyk] Security upgrade @angular-devkit/build-angular from 22.0.4 to 22.0.7 - #2

Open
pharret31 wants to merge 1 commit into
26_1from
snyk-fix-14da6f06dbc8ce331f8afbb226952e4a
Open

[Snyk] Security upgrade @angular-devkit/build-angular from 22.0.4 to 22.0.7#2
pharret31 wants to merge 1 commit into
26_1from
snyk-fix-14da6f06dbc8ce331f8afbb226952e4a

Conversation

@pharret31

Copy link
Copy Markdown
Owner

snyk-top-banner

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

Snyk changed the following file(s):

  • apps/demos/package.json
⚠️ Warning
Failed to update the pnpm-lock.yaml, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue
high severity Allocation of Resources Without Limits or Throttling
SNYK-JS-WS-17988732

Breaking Change Risk

Merge Risk: Low

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

@pharret31

Copy link
Copy Markdown
Owner Author

Merge Risk: Low

This is a patch version upgrade for @angular-devkit/build-angular from v22.0.4 to v22.0.7. Patch releases typically include bug fixes and minor improvements without introducing breaking changes.

It is important to note that starting with Angular v22, the @angular-devkit/build-angular package and its Webpack support are deprecated. The recommended replacement is the esbuild and Vite-based @angular/build package. While this patch update itself is low risk, developers should plan for the future migration away from this deprecated package.

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

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