Repository navigation
chore(release): prepare MCP 1.0.15 - #150
Merged
Merged
Conversation
Bumps the workspace, npm package, MCP Registry metadata, and the boundary self-test to 1.0.15, and adds the 1.0.15 changelog covering the one commit on main since v1.0.14: resume and resume_list exclude the session id the API assigned at init (3c99506), which the 1.0.14 exclusion did not do in production. No dependency changes: Cargo.lock differs from 1.0.14 only in the seven workspace package versions. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com> Signed-off-by: escott- <escott05@gmail.com>
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.
Bumps the workspace, npm package, MCP Registry metadata, and the boundary self-test to 1.0.15, and adds the 1.0.15 changelog covering the one commit on
mainsince v1.0.14:3c99506resumeandresume_listnow exclude the session id the API assigned atinit. The 1.0.14 exclusion did not work in production when the caller passed nosession_id: the server kept a random local id while the API stores snapshots under the id it returns frominit, which was never read.No dependency changes:
Cargo.lockdiffers from 1.0.14 only in the seven workspace package versions (anstyleis a third-party crate that happens to sit at 1.0.14 and is untouched).Verification
On ovh-desktop, against
main3c99506 plus this change:cargo fmt --all --checkcargo clippy --locked --workspace --all-targets -- -D warningscargo test --locked --workspace --all-targets: 2961 passed, 0 failed (2958 before, plus the 3 new tests from the fix, includingresume_after_a_real_init_never_offers_the_session_the_api_just_opened)account_connection_smoke.pyagainst the built binary: 9 testscargo audit --deny warningsandcargo deny --locked check: cleanOn a clean copy of the tracked files:
public_boundary.py,release_contract.py resolve-versionforv1.0.15, the release-contract, boundary, DCO, workflow, grounding and adoption script tests, andnpm test(6/6).No macOS-only code changed in this release, so no separate macOS gate was run; the darwin release builds compile the whole crate.
Not verified: the fix against production. After installing 1.0.15, a fresh session calling
session(action="resume")with no arguments should return the previous session, not itself.🤖 Generated with Claude Code
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.