update package-lock test #271
Merged
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.
Note
Low Risk
CI-only changes limited to workflow triggers and npm lockfile validation; main risk is false failures due to Node/npm version differences or lockfile regeneration behavior.
Overview
The
check-package-lockGitHub Actions workflow now only runs whenpackage.jsonorpackage-lock.jsonchange (onmainpushes and all PRs), reducing unnecessary CI runs.It upgrades the job to Node
20.xand adds a PR-only step that regeneratespackage-lock.json(npm install --package-lock-only) and fails the build if the committed lockfile is out of date relative topackage.json.Written by Cursor Bugbot for commit 4030151. This will update automatically on new commits. Configure here.