Sync package-lock.json with the 0.5.1 bump - #87
Merged
Conversation
The version bump edited package.json without running npm install, so the lockfile's two root version fields stayed at 0.5.0 and every npm i regenerated the sync as a dirty diff.
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.
Closes #86
The 0.5.1 bump edited
package.jsonand the manifests without runningnpm install, leaving the lockfile's two root version fields at 0.5.0; everynpm iregenerated the sync as a dirty working-tree diff. This commits the two-line sync npm produces.Nothing functional depends on it (
npm cipasses despite the mismatch, and the store zips exclude the lockfile), but it should land before taggingv0.5.1so the release tag points at a self-consistent tree.🤖 Generated with Claude Code