Skip to content

Bump the crates to 0.6.0 - #217

Merged
aterga merged 1 commit into
mainfrom
arshavir/bump-0.6.0
Oct 28, 2026
Merged

aterga merged 1 commit into
mainfrom
arshavir/bump-0.6.0

Conversation

@aterga

@aterga aterga commented Oct 28, 2026

Copy link
Copy Markdown
Collaborator

Summary

The version bump that precedes cutting a release candidate, per CONTRIBUTING's "Releasing": all three crates (imcp2, imcp2-core, imcp2-local) share one version, and deploy-candidate.yml refuses an rc-* tag whose version does not match every Cargo.toml.

A minor bump, not a patch: 0.6.0 carries the financial guard's new scopes from #213, #214 and #215. Update calls that 0.5.1 allowed are refused now (any method name carrying a financial keyword, every update to a canister whose interface declares ICRC-1/ICRC-2 methods, and every update to a canister whose interface is missing or unreadable), which is a behaviour change for anyone embedding the crate.

Related issues

Follows #213, #214 and #215. Next steps after merge, per the release procedure: git tag rc-0.6.0-1 <this commit on main> to deploy staging, then git tag v0.6.0 rc-0.6.0-1^{} to promote.

Changes

  • Cargo.toml: version and the workspace pin imcp2-core = { path = …, version = … } to 0.6.0
  • crates/imcp2-core/Cargo.toml, crates/imcp2-local/Cargo.toml: version to 0.6.0
  • Cargo.lock: refreshed with cargo update -w; only the three workspace entries change

Same shape as the previous bump (#205).

Testing

  • cargo metadata --locked resolves for the whole workspace (the lockfile is consistent under --locked)
  • cargo test --locked -p imcp2-core --lib: 203 passed, 0 failed
  • cargo fmt --all -- --check clean
  • cargo build --locked --all-targets for the whole workspace was not run locally; CI's test job covers it
  • npm test --prefix monitoring/mcp-status (dashboard unchanged)

Checklist

  • I have read the Contributing guidelines.
  • Docs (README / comments) updated for any user-visible change. (None: a version bump; the submission log in docs/anthropic-directory-submission.md still says 0.5.1 and is best updated when the candidate and release tags are cut.)
  • No secrets, credentials, or internal-only information are included.

Generated by Claude Code

All three crates share one version. The minor bump carries the financial
guard's new scopes (#213, #214, #215): update calls that 0.5.1 allowed —
any method name carrying a financial keyword, every update to a canister
whose interface declares ICRC-1/ICRC-2 methods, and every update to a
canister whose interface is missing or unreadable — are refused now,
which is a behaviour change for anyone embedding the crate.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PruVfYuaS7ZAgNBMTsuRP6
@aterga
aterga requested a balanced review from Copilot October 28, 2026 15:48
@aterga
aterga marked this pull request as ready for review October 28, 2026 15:48
@aterga
aterga requested a review from a team October 28, 2026 15:48

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟢 Approval recommended

No active review issues are reported for the 0.6.0 release-candidate metadata update.

No open issues 🎉

What changed in this PR

Prepares the workspace for the 0.6.0 release candidate. The minor version bump reflects the stricter financial-transaction guard introduced in #213–#215; this PR changes version metadata only.

Changes:

  • Bumps all three crates from 0.5.1 to 0.6.0.
  • Aligns the shared imcp2-core dependency requirement with 0.6.0.
  • Updates only the three workspace package versions in Cargo.lock.
File Description
crates/​imcp2-local/​Cargo.toml Bumps the local server crate to 0.6.0.
crates/​imcp2-core/​Cargo.toml Bumps the shared core crate to 0.6.0.
Cargo.toml Bumps the server crate and shared core dependency requirement to 0.6.0.
Cargo.lock Synchronizes all three workspace package versions.

Review effort: Balanced

@aterga
aterga merged commit d9f0f62 into main Oct 28, 2026
17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants