fix: sync root package-lock.json with package.json#383
Merged
Conversation
The root package.json declares @actions/exec ^3.0.0 (and transitively @actions/io ^3.0.2), but the committed lock still pinned @actions/exec 1.1.1 / @actions/io 1.1.3, left over from an earlier dependency bump. This makes `npm ci` fail (EUSAGE: package.json and package-lock.json out of sync), breaking the unit-test job on every PR. Regenerated with `npm install --package-lock-only`; `npm ci` now passes. Only the top-level @actions/exec/@actions/io entries change; @actions/core keeps its own nested 1.1.x copies. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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
2 participants
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.
Summary
The root
package.jsondeclares@actions/exec: ^3.0.0(and transitively@actions/io: ^3.0.2), but the committedpackage-lock.jsonstill pinned@actions/exec@1.1.1/@actions/io@1.1.3— left over from an earlier dependency bump where the lock wasn't regenerated.This makes
npm cifail withEUSAGE: package.json and package-lock.json … out of sync, which breaks the unit-test job on every PR (and on main).Fix
Regenerated the lock with
npm install --package-lock-only. Only the top-level@actions/exec/@actions/ioentries change (→ 3.0.0 / 3.0.2);@actions/corekeeps its own nested 1.1.x copies.Verification
npm cinow succeeds (previously EUSAGE).package-lock.json), +21/-13.🤖 Generated with Claude Code