Skip to content

[Snyk] Security upgrade @angular/common from 8.0.0 to 19.2.16 - #53

Open
DaSchTour wants to merge 1 commit into
masterfrom
snyk-fix-f067061ee2c12bbbf7cb5b5bddf3609b
Open

[Snyk] Security upgrade @angular/common from 8.0.0 to 19.2.16#53
DaSchTour wants to merge 1 commit into
masterfrom
snyk-fix-f067061ee2c12bbbf7cb5b5bddf3609b

Conversation

@DaSchTour

Copy link
Copy Markdown
Owner

snyk-top-banner

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

Snyk changed the following file(s):

  • package.json
⚠️ Warning
Failed to update the package-lock.json, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Insertion of Sensitive Information Into Sent Data
SNYK-JS-ANGULARCOMMON-14135651
  671  

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.

Copilot AI review requested due to automatic review settings November 28, 2025 12:08

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR attempts to fix a high-severity security vulnerability (SNYK-JS-ANGULARCOMMON-14135651) by upgrading @angular/common from version 8.0.0 to 19.2.16. However, this approach will cause critical compatibility issues as it only upgrades a single Angular package while leaving all other Angular framework packages at version 8.

Key Changes

  • Upgrades @angular/common from ~8.0.0 to ~19.2.16 (an 11 major version jump)
  • No changes to other Angular packages or dependencies
  • Package-lock.json update failed (as noted in the PR warning)

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread package.json
"dependencies": {
"@angular/animations": "~8.0.0",
"@angular/common": "~8.0.0",
"@angular/common": "~19.2.16",

Copilot AI Nov 28, 2025

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Upgrading only @angular/common to version 19.2.16 while keeping all other Angular packages at version 8.0.0 will cause severe peer dependency conflicts and application failure. Angular packages must be upgraded together as they have strict peer dependency requirements.

All Angular packages should be upgraded to the same major version:

  • @angular/animations: ~8.0.0
  • @angular/compiler: ~8.0.0
  • @angular/core: ~8.0.0
  • @angular/forms: ~8.0.0
  • @angular/platform-browser: ~8.0.0
  • @angular/platform-browser-dynamic: ~8.0.0
  • @angular/router: ~8.0.0

Additionally, devDependencies like @angular/cli, @angular/compiler-cli, and build tools must also be upgraded to match.

Consider using Angular's update guide (https://update.angular.io/) to perform a proper incremental upgrade from version 8 to 19, addressing breaking changes at each major version.

Suggested change
"@angular/common": "~19.2.16",
"@angular/common": "~8.0.0",

Copilot uses AI. Check for mistakes.
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.

3 participants