chore(release): 0.6.20 - #110
Merged
Merged
Conversation
Why this change was needed: Ships the MCP stdio handshake fix (#108, closing #107) to users. The reporter and anyone else on a client that probes before `initialize` cannot connect at all until there is a tagged release: `npx @webclaw/mcp` installs a prebuilt binary pinned to the latest tag, so a fix sitting on main is not reachable by them. Cut as a patch on its own rather than waiting for the PDF artifact work in #105, which adds `#[non_exhaustive]` to a public enum and is therefore a breaking release. Holding an external user's connectivity fix behind that would serve nobody. What changed: - [workspace.package] version 0.6.19 -> 0.6.20 (all 7 crates inherit it) - Cargo.lock regenerated - CHANGELOG: the Unreleased entry becomes [0.6.20] - 2026-08-16 No code changes; this is the version bump only. Problem solved: Tagging v0.6.20 publishes the binaries and republishes @webclaw/mcp pinned to the new tag, so affected clients connect without a client-side shim.
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.
Version bump only, no code changes.
Ships the MCP stdio handshake fix from #108 (closing #107). Until there is a tagged release the fix is unreachable for affected users:
npx @webclaw/mcpinstalls a prebuilt binary pinned to the latest tag.Cut on its own rather than waiting for #105, which adds
#[non_exhaustive]to a public enum and is therefore a breaking release.[workspace.package]version 0.6.19 → 0.6.20, inherited by all 7 cratesCargo.lockregeneratedUnreleasedentry becomes[0.6.20] - 2026-08-16packages/create-webclawand@webclaw/mcpneed no manual bump: the release workflow's npm job pins the launcher to the new tag and publishes the next patch above whatever is on npm.After merge, pushing
v0.6.20triggers the release workflow (binaries → GitHub release → npm, Docker, Homebrew).