fix(ci): sync Angular peer deps and add --legacy-peer-deps to npm ci#434
Open
fix(ci): sync Angular peer deps and add --legacy-peer-deps to npm ci#434
Conversation
After dependabot bumped @angular/core and @angular/compiler to 20.3.18 in separate PRs, other Angular packages remained at 20.3.17 in the lockfile. npm 11 strict peer-dep checking caused `npm ci` to fail with a conflicting peer dependency error. - Update package.json: align all @angular/* deps to ^20.3.18 - Regenerate package-lock.json with consistent Angular 20.3.18 versions - Add --legacy-peer-deps to npm ci in CI workflow to prevent future peer-dep conflicts when dependabot bumps Angular packages individually Co-Authored-By: Paperclip <noreply@paperclip.ing>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
After dependabot bumped @angular/core and @angular/compiler to 20.3.18 in separate PRs, other Angular packages remained at 20.3.17 in the lockfile. npm 11 strict peer-dep checking caused
npm cito fail with a conflicting peer dependency error.