Repository navigation
chore: release 0.30.1 - #982
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
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 v0.30.1
Bump
@fastagent-sh/fastagentfrom 0.30.0 to 0.30.1. Two fixes to 0.30.0; nothing else.Fixed
-vprinted the version and did nothing (fix(cli): a program option is read only before the command, so a value that begins with -v is never the version #981). commander read the program's-v, --versionanywhere in the arguments by default, sofastagent invoke "-very urgent: …",--name -vendorandinvoke --session <id>with an id beginning with-v(1 storage in 4096) printed0.30.0and exited 0 having done nothing. The program's options are now read only before the command, asdocs/cli.mdsays; an operand that begins with-after the command is refused as an unknown option (exit 2).--check <ticket> --stop), replacing it with a newer attempt, or giving up on its start signalled the step and wrote the reason after; a step that heard the consequences first (its host CLI killed by the same signal, assignal-exitlets it on Linux) recorded its own failure, and that one stayed. A ticket's end is now written once, before what it decides is done, and nothing the step writes after reopens it.Verification
npm run lint,npm run typecheck,npm test(195 files, 2382 passed, 2 skipped),npm pack --dry-run --json.After merge
Create and publish the GitHub Release
v0.30.1from the merged commit, with the sections above as its notes. The protected publish workflow verifies and publishes the package to npm via Trusted Publishing. This PR itself does not tag or publish.