Repository navigation
Bump the crates to 0.5.0 - #199
Merged
Merged
Conversation
The v0.5.0 tag was pushed at 62fee9c while every manifest still said 0.4.0, so the publish workflow's first check refused it. This is the release that carries Client ID Metadata Documents (#191) and the on-host /metrics assertion (#198). imcp2-local moves in lockstep as before, and the workspace dependency on imcp2-core follows. Cargo.lock refreshed with `cargo update -w`; build and tests pass with --locked. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Xd7VT72Qt16qiAJynu9EKj
There was a problem hiding this comment.
Copilot review overview
🟢 Approval recommended
All workspace manifests, dependency pins, and lockfile entries are consistently updated.
Review effort: Balanced
Findings: None
What changed in this PR
Updates all workspace crates to the 0.5.0 release version.
Changes:
- Bumps
imcp2,imcp2-core, andimcp2-localto0.5.0. - Aligns the workspace dependency and lockfile entries.
| File | Description |
|---|---|
Cargo.toml |
Updates the main crate and core dependency versions. |
crates/imcp2-core/Cargo.toml |
Bumps imcp2-core to 0.5.0. |
crates/imcp2-local/Cargo.toml |
Bumps imcp2-local to 0.5.0. |
Cargo.lock |
Synchronizes workspace package versions. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
sea-snake
approved these changes
Sep 23, 2026
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
v0.5.0tag was pushed at 62fee9c while every manifest still said0.4.0, so the publish workflow's first check refused it (run 35918795624:tag v0.5.0 does not match imcp2-core's Cargo.toml version 0.4.0). This bumpsimcp2,imcp2-coreandimcp2-localto0.5.0— in lockstep, as0.4.0was — the workspace dependency onimcp2-corewith them, and the three lines inCargo.lock. It is the release that carries Client ID Metadata Documents (#191) and the on-host/metricsassertion (#198).After merge the tag has to move. The workflow also requires the tagged commit to be on
main, and the existing tag points at a commit without this bump, so it must be deleted and re-created on the merge commit; the push of the new tag re-triggers "Publish crate":imcp2-local's dist release listens on its ownimcp2-local-v*tag namespace, so its bump here publishes nothing by itself.Related issues
Follows #191 and #198.
Changes
Cargo.toml—imcp2to0.5.0; the workspace dependencyimcp2-coreto0.5.0.crates/imcp2-core/Cargo.toml,crates/imcp2-local/Cargo.toml—0.5.0.Cargo.lock— the three workspace entries, viacargo update -w; no other dependency moves.Testing
cargo build --locked --workspace --all-targetscargo test --locked --workspace --all-targets— 297 tests, 0 failurescargo publish --locked --dry-run --workspace— the workflow's Package step: both crates package and verify. One pre-existing warning it prints:chacha20 v0.10.0inCargo.lockis yanked on crates.io. Unrelated to this change and not fatal to publishing, but worth acargo update -p chacha20in a follow-up.cargo metadatareports0.5.0forimcp2-coreandimcp2, the check the failed job ran.github/scripts/scan-internal-identifiers.sh origin/main...HEAD— cleancargo fmt/cargo clippy: no Rust source changed.npm test: the dashboard is unchanged.Checklist
🤖 Generated with Claude Code
https://claude.ai/code/session_01Xd7VT72Qt16qiAJynu9EKj
Generated by Claude Code