Repository navigation
Composer: require stable mcp/sdk ^0.8.1 (v0.3.0) - #8
Merged
Merged
Conversation
TraceableRegistry follows the new RegistryInterface, Psr16StoreSession is renamed to Psr16SessionStore, Resource to ResourceDefinition and StreamableHttpTransport no longer takes a CORS headers argument.
f3l1x
force-pushed
the
chore/release-prep
branch
from
October 2, 2026 21:31
b265411 to
283f2b6
Compare
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
Moves
mcp/sdkfrom thedev-main#3699323…commit pin to the stable^0.8.1release, with the code changed to match the new API.TraceableRegistrynow matches the newRegistryInterface:register*()return their references.unregister*()andhas*()methods.clear()andget/setDiscoveryState()are removed.Resourceis renamed toResourceDefinition.Psr16StoreSessionis renamed toPsr16SessionStore.StreamableHttpTransportno longer takes the$corsHeadersargument, so the transport now uses the SDK's default middleware.nette/diandsymfony/findermove torequire.symfony/finderis needed for file-based discovery. The optional integrations (application, http, console, tracy) are listed undersuggest.0.3.x-devand adds the version table to the README.BuilderMan, thetempDirtype check, Nette header handling inGuzzleBridge.Commits
QA
make cs: passesmake phpstan(level 9): passesmake tests: 12 tests passcomposer update --prefer-lowest, then tests and phpstan: pass (mcp/sdk 0.8.1, nette/di 3.2.5, nette/http 3.3.3, nette/application 3.2.8)Needs a decision before release
With the SDK default middleware,
StreamableHttpTransportnow runsDnsRebindingProtectionMiddleware(on top of CORS and protocol-version validation). Its allowlist only includeslocalhost,127.0.0.1and[::1].GuzzleBridgeforwards the realHost/Originheaders, so a non-localhost deployment of the HTTP transport will get403 Forbidden: Invalid Host header. We probably need anallowedHosts(ormiddleware) option in the extension, or at least a documented customTransportFactory. This PR does not include that yet.Proposed version:
v0.3.0v0.2.0was tagged from master before this PR (with the olddev-mainpin), so this becomesv0.3.0.This is a breaking change within 0.x. The public
TraceableRegistryAPI and the SDK types users touch have changed, the SDK HTTP security defaults now apply, and there are new runtime requirements.Draft release notes (v0.2.0...v0.3.0)
Breaking
mcp/sdk^0.8.1instead of thedev-maincommit pin. Attribute-based tools, resources and prompts work as before, but code that uses the SDK API directly may need changes (for exampleResourceis nowResourceDefinitionandPsr16StoreSessionis nowPsr16SessionStore).TraceableRegistryfollows the newRegistryInterface:register*()return references,unregister*()/has*()are added, andclear()and the discovery-state methods are removed.nette/diandsymfony/finderare now required at runtime.Fixes
BuilderMantempDirand header types reported by phpstan (fixes red phpstan on master)Docs / Chore
Not tagging or releasing yet. That is left to the maintainer.