Repository navigation
Bump the crates to 0.6.1 - #228
Merged
Merged
Conversation
All three crates share one version. A patch bump: nothing since 0.6.0 changes the crates' public API or refuses anything 0.6.0 allowed. It carries the mcp_get_delegation retry on a lagging replica (#220), the bound on what one /oauth/authorize request stores (#221), the reworded open_app and call tool descriptions and server instructions (#226), and clippy fixes (#224). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
sea-snake
approved these changes
Nov 3, 2026
There was a problem hiding this comment.
🟢 Approval recommended
No active review issues are recorded for the release-metadata update.
No open issues 🎉
What changed in this PR
Prepares the workspace for the 0.6.1 release candidate by updating all three crates together, following the same version-bump pattern as 0.6.0. This PR changes release metadata only.
Changes:
- Bumps
imcp2,imcp2-core, andimcp2-localto 0.6.1. - Updates the workspace’s
imcp2-coredependency requirement to 0.6.1. - Synchronizes the three workspace entries in
Cargo.lockwithout changing external dependencies.
| File | Description |
|---|---|
crates/imcp2-local/Cargo.toml |
Bumps the local server crate to 0.6.1. |
crates/imcp2-core/Cargo.toml |
Bumps the shared core crate to 0.6.1. |
Cargo.toml |
Bumps the root crate and shared core dependency requirement to 0.6.1. |
Cargo.lock |
Records 0.6.1 for all three workspace packages. |
Review effort: Balanced
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
The version bump that comes before cutting a release candidate, following "Releasing" in CONTRIBUTING. All three crates (
imcp2,imcp2-core,imcp2-local) share one version, anddeploy-candidate.ymlrefuses anrc-*tag whose version doesn't match everyCargo.toml.This is a patch bump, not a minor one: nothing since
v0.6.0changes the crates' Rust public API. That covers #227 too, because the types it changes live inimcp2-core's privatecallsmodule, so code embedding the crate still compiles unchanged.#227 merged after this branch was cut and before the bump merged, so it's in 0.6.1 (and in
rc-0.6.1-1). It does change whatget_canister_candidreturns to MCP clients, and it refuses something 0.6.0 allowed:methods: called withoutmethods, an interface over 5 KB is now refused, with a list of every method the service declares. In 0.6.0 the full interface came back.structuredContentno longer carriescandid. The interface text is only in the reply's text content. The structured content now describes that text withmethods,bytesandbest_effort.methods: ["<name>", …]returns only those methods, with every type definition they use and the interface's own comments.#217 bumped the minor version for this kind of change, but we're keeping 0.6.1 on purpose, since embedders' code doesn't break. Anyone who reads
structuredContent.candidshould switch to the text content.The release includes:
get_canister_candidcan read just the methods you name, and refuses a large interface without them (see above)mcp_get_delegationwhen a replica that's behind answersNoSuchDelegation/oauth/authorizerequest stores in its pending connectopen_app,canister_queryandcanister_update_calldescriptions and for the server instructionsRelated issues
Follows #217, the 0.6.0 bump. Next steps after merge, per the release procedure: run
git tag rc-0.6.1-1 <this commit on main>to deploy staging, thengit tag v0.6.1 rc-0.6.1-1^{}to promote.Changes
Cargo.toml:version, and the workspace pinimcp2-core = { path = …, version = … }, set to 0.6.1crates/imcp2-core/Cargo.toml,crates/imcp2-local/Cargo.toml:versionset to 0.6.1Cargo.lock: refreshed withcargo update -w; only the three workspace entries changeSame shape as the 0.6.0 bump (#217).
Testing
The local checks below ran on this branch, which was cut before #227 merged. CI on the merge commit
278cc19(the commitrc-0.6.1-1points at), which has both #227 and the bump, passed.cargo metadata --lockedresolves for the whole workspace, so the lockfile is consistent under--lockedcargo check --locked --workspace --all-targets: finishes with no warningscargo test --locked -p imcp2-core --lib: 206 passed, 0 failedcargo fmt --all -- --check: cleancargo test --locked --all-targetsfor the whole workspace andcargo clippyweren't run locally; CI's jobs cover themnpm test --prefix monitoring/mcp-status: dashboard unchangedChecklist
docs/still say 0.6.0 and are best updated once the candidate and release tags are cut.)🤖 Generated with Claude Code