Repository navigation
chore: prepare agent-cli 0.2.0 for release - #51
Merged
Merged
Conversation
3 tasks
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.
The release guard requires the pending Changesets to be consumed before a stable tag can publish. Apply the validated version patch from Version packages run 38948917469 to prepare
@bloxwap/[email protected].Package, lockfile, changelog, packaged/embedded skill and generated docs now agree. Skill version synchronization also updates the command's example output, with a regression assertion that it matches the package. The lock changes only the CLI workspace version; dependency resolutions are unchanged.
Validated build, lint, typecheck, all 103 offline CLI tests, docs checks and script-free global npm/installed bunx smoke at 0.2.0. Publication remains pending npm configuration and live acceptance evidence described in #11, #37, #39, #40 and #41. No version tag or package publication is part of this PR.
Refs #40, #41. Follows #50.