Regenerate package-lock.json with npm 11#86
Merged
Conversation
- Regenerate package-lock.json with npm 11 for stricter validation - Add npm upgrade to pr-checks.yaml to match publish.yml npm 11 has stricter lockfile validation than npm 10 (bundled with Node 22).
pcholakov
force-pushed
the
pavel/soqnpttmvwnt
branch
from
a73eae4 to
ae5b0c9
Compare
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
npm 11 has stricter lockfile validation and requires the lockfile to be generated with npm 11+ for compatibility.