release: v0.3.2 — MCP 2026-07-28 tools/list cache metadata - #72
Merged
Conversation
0.3.1 omitted the SEP-2549 `ttlMs` and `cacheScope` fields from `tools/list`, which the 2026-07-28 spec requires. Hosts that negotiate that version — Claude Code 2.1.234 among them — rejected tool discovery outright, so an installed 0.3.1 advertises no tools at all to them (#68). Ships #69: both fields are set on the `list_tools` override behind a named TTL, and pre-2026-07-28 peers keep their existing wire shape.
![revuto-review[bot]](https://avatars.githubusercontent.com/u/55848801?s=60&v=4){kind=small}
There was a problem hiding this comment.
This is an auto review done by revuto.
Revuto completed the review and found no evidence-backed concerns.
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.
Summary
Cuts 0.3.2 so the #68 fix reaches installed users. 0.3.1 omitted the SEP-2549
ttlMsandcacheScopefields fromtools/list, which the 2026-07-28 spec requires — hosts negotiating that version, Claude Code 2.1.234 among them, reject tool discovery outright, so an installed 0.3.1 advertises no tools at all to them.Ships #69. Version-only change:
Cargo.toml,Cargo.lock,npm/package.json, same three-line shape as the v0.3.1 bump (96f7f30).Checklist
cargo fmt --checkpassescargo clippy --locked -- -D warningspassescargo test --lockedpasses (180 tests)git diff --checkis cleanscripts/integration_smoke.sh— N/A, no behavior change in this commit; the shipped fix was smoke-verified on fix(server): add MCP 2026-07-28 support #69Verification
Ran what CI runs, plus the release-specific gates:
cargo fmt --checkcargo build --lockedcargo clippy --locked -- -D warningscargo test --lockedscripts/install_smoke.shinstaller smoke ok(release profile)node --checkoverscripts/,npm/node --test npm/scripts/postinstall.test.js0.3.2 == 0.3.2npm pack --dry-runagent-sh-agent-workspace-linux-0.3.2.tgz, 4 filesAfter merge
Tag
v0.3.2on the merge commit and push it. That builds both targets, attaches the binaries with their.sha256sidecars, then publishes the npm wrapper with the version stamped from the tag.