chore(release): 0.4.4#148
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
from
c78011d to
0c0feb2
Compare
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
from
0c0feb2 to
4c9515d
Compare
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 next agent-tty release. Merging this PR creates the release tag and GitHub Release and starts the publish pipeline.
[0.4.4] - 2026-06-12
Documentation
0–11) indocs/USAGE.md, add an exit-codes section, and clarify that a standalonewaittimeout exits0withtimedOut: truein the JSON envelope while exit code11(WAIT_TIMEOUT) only surfaces from a fail-fastbatch. Restructure the README with anchor nav, a numbered "canonical loop" Quickstart, and a grouped command-surface table (#150 by @ThomasK33).Changed
feat:commits now bump the minor version (e.g.0.4.x→0.5.0) instead of being flattened into patch releases.fix:still bumps patch, and breaking changes still bump minor rather than jumping to 1.0.0 — reaching 1.0.0 remains an explicitRelease-As: 1.0.0decision (#152 by @ThomasK33).Fixed
release-please--branches--maininstead ofrelease-please--branches--main--components--agent-tty. The stock node strategy embedded the component name in the branch even withinclude-component-in-tag: false;CommuniqueNodeStrategynow overridesgetBranchComponent()so the branch follows the tag setting. Any release PR still open on the old component-suffixed branch must be closed (not merged) — merging it would silently skip release creation due to the component mismatch inbuildRelease()(#147 by @ThomasK33).Maintained by the release-please workflow. Notes are regenerated by Communique on every push to main, so manual edits to this PR are overwritten.