Repository navigation
chore(release): prepare 2.3.0 - #252
Merged
Merged
Conversation
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.
Prepare 2.3.0 across the five lockstep CLI packages and seven bundled Skills. Add matching English and Chinese release notes for Pi integration, global flag placement and validation, bilingual parser errors, and configurable temporary OSS upload timeouts.
Synchronize the npm package READMEs with the root documentation and simplify the MCP setup description.
Validation:
pnpm exec vp check: passed with 0 errors and 3 existing warnings.CI=true node tools/release/publish-stable.mjs --knowledge --dry-run: passed for all five packages, including builds, packaging, publint, and gitleaks.