fix: update lockfile version to 3 for npm compatibility#13
Merged
Conversation
npx cccsc@latest add was creating lockfiles with version 1, but current npm versions expect version 3. Added CURRENT_LOCKFILE_VERSION constant to replace magic number. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
hiragram
enabled auto-merge
July 3, 2025 06:28
Update test assertion to match the new lockfile version constant. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <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
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.
Summary
npx cccsc@latest addwas creating lockfiles with version 1CURRENT_LOCKFILE_VERSIONconstantTest plan
npx cccsc@latest addand verify lockfile version is 3🤖 Generated with Claude Code