chore: set package version to 2.5.1#75
Merged
Merged
Conversation
Sync the manifest version (and package-lock root entries) with the v2.5.1 release tag. The version had been left at 1.0.0, decoupled from the tag scheme; this brings package.json in line so the manifest tracks releases going forward. 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
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.
Sync manifest version to 2.5.1
The
package.jsonversion had been left at1.0.0, decoupled from the git tag scheme (tags are atv2.5.1). This brings the manifest — and thepackage-lock.jsonroot entries — in line with the latest release tag, so the manifest tracks releases going forward.package.json:1.0.0→2.5.1package-lock.json: rootversionentries (top-level +packages[""]) updated to match; dependency versions untouched.🤖 Generated with Claude Code