Skip to content

[Snyk] Security upgrade @angular/common from 6.1.10 to 19.2.16 #72

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.

Sign up for GitHub

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
codeztech-atique wants to merge 1 commit into
base: master
Choose a base branch
from
Open

[Snyk] Security upgrade @angular/common from 6.1.10 to 19.2.16 #72

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,7 +13,7 @@
"dependencies": {
"@angular/animations": "^6.1.8",
"@angular/cdk": "^6.4.7",
"@angular/common": "^6.0.3",
"@angular/common": "^19.2.16",
"@angular/compiler": "^6.0.3",
"@angular/core": "^6.0.3",
Comment on lines 14 to 18
Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot Nov 28, 2025

Choose a reason for hiding this comment

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

P1 Badge Keep Angular packages on same major version

Only @angular/common is bumped to ^19.2.16 while the rest of the Angular stack (core, compiler, CLI, etc.) remains on v6, and package-lock still pins v6.1.10; Angular packages declare peer dependencies on the same major version, so installing or running the app now hits peer-dependency conflicts (and npm ci will fail because the lockfile no longer matches package.json). Upgrade the full Angular suite together or keep @angular/common on the v6 line and regenerate the lockfile.

Useful? React with 👍 / 👎.

"@angular/forms": "^6.0.3",
Expand Down