Repository navigation
chore(release): prepare 0.15.0 - #41
Merged
Merged
Conversation
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
Prepare 0.15.0 for the merged contract-alignment changes and BYOC MCP tunnel support in #42. The release branch now contains current main
c96ba135372ed91cc1b733ed62390c807f912badand keeps an empty Unreleased section.The version notes include Managed Session creation, Forward Template inheritance, and Managed Deployment tunnel binding, including replace/clear update semantics. Existing breaking-change and migration guidance remains included.
Why
Ship the already merged API alignment and BYOC changes together in the selected minor release, with matching package versions and release notes.
Verification
npm run buildnpm run typechecknpm testnpm run docs:checknpm pack --dry-runNode 22: 4,461 tests passed, zero failures or skips.
The feature-main QA package was already checked through internal integration, nine live tunnel-binding cases per SDK, and Global Managed/Forward authenticated MCP discovery. Service logs confirmed tunnel routing and 24 discovered tools per Session. These feature-package results do not replace QA of the final version-merge SHA. No business MCP tool calls were performed.
Impact
This PR changes release metadata relative to current main. After merge and successful main CI, rebuild and accept version QA packages from that exact SHA before formal publication.