build(deps): bump angular/core and /compiler to 20.3.16 #508
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Review changes with |
Member
Author
|
Meh, this installed on my machine using node 22, but it's not installing here in CI with node 24. I guess I'll have to test node 24 locally. |
Contributor
|
This was referenced Jan 12, 2026
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
bump angular/core and /compiler to 20.3.16 and other peers that have to come along, plus rebuild a fresh package-lock.json because otherwise the npm install just fails.
Replaces #505 and #506
PR Goal?
Handle CVEs in @angular/core and @angular/compiler <= 20.3.15
Fixes?
Those CVEs
Feedback sought?
rubber stamping, as CI's output is what I mostly want
Priority?
High according to the dependabot alerts...
Tests added?
no
How to test?
I'm assuming if the PR preview runs, that's good enough.
Confidence?
medium-high
Version change?
no