fix: sync package-lock.json version to 0.1.2#5
Merged
Conversation
The lockfile root version remained at 0.1.0 after the v0.1.2 bump, so `npm install` and lockfile-aware tooling reported a mismatched root package version. `package-lock.json` is not included in the published npm tarball (the `files` allowlist excludes it), so this only affects the development checkout and CI installs — no v0.1.3 release needed. Addresses review feedback on #4 from copilot-pull-request-reviewer. Signed-off-by: Sebastian Mendel <sebastian.mendel@netresearch.de>
There was a problem hiding this comment.
Copilot wasn't able to review any files in this pull request.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
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
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 lockfile root version remained at
0.1.0after the v0.1.2 bump in #4 —npm installand lockfile-aware tooling reported a mismatched root package version.Why no v0.1.3 release
package-lock.jsonis not in the published npm tarball (verified againstdist.tarballfor v0.1.2 — thefilesallowlist only includessrc/ bin/ LICENSE README.md CHANGELOG.md). This bug only affects the repo checkout, CI installs, and contributors — npm consumers are unaffected, so no version bump is needed.Addresses
Resolves copilot-pull-request-reviewer feedback on #4 (#4 (comment)).
Test plan
npm install --package-lock-onlyregenerates cleannpm cino longer warns about version mismatch