chore(release): sync package-lock.json to 0.1.25.61#190
Merged
Conversation
PR #189 bumped package.json to 0.1.25.61 but left the lockfile's top-level version at .60. Regenerated via `npm install --package-lock-only` — only the two version fields change, no dependency tree churn. Keeps the release-version alignment the release process requires before tagging.
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.
Release-prep follow-up to #189, which bumped
package.jsonto0.1.25.61but leftpackage-lock.jsonat.60. Regenerated withnpm install --package-lock-only— only the two top-level version fields change, no dependency-tree churn.Restores the version alignment the release process requires before tagging
v0.1.25.61.