fix(deps): update module github.com/modelcontextprotocol/go-sdk to v0.8.0 #66
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.
This PR contains the following updates:
v0.5.0
->v0.8.0
Release Notes
modelcontextprotocol/go-sdk (github.com/modelcontextprotocol/go-sdk)
v0.8.0
Compare Source
This release exists to include the API change from #518, mentioned in the v0.7.0 release. It also includes a small change to remove extraneous API.
This concludes our API audit. Barring a realization over the weekend, we will cut v1.0.0 and any further API changes will be handled in a backwards compatible way.
API Changes
any
, to decouple the SDK's API from thegithub.com/google/jsonschema-go/jsonschema
package. Now that package is only used for inference (inmcp.AddTool
) and validation.Full Changelog: modelcontextprotocol/go-sdk@v0.7.0...v0.8.0
v0.7.0
Compare Source
This release fixes a couple bugs related to the
StreamableClientTransport
, and relaxes it to be less strict so that it can talk to certain servers that don't perfectly conform to the spec. It also updates togoogle/[email protected]
, which includes a couple backwards incompatible bug fixes (see below).For more details, see the v0.7.0 milestone.
API Changes
No changes in the API of the SDK itself, but the updated google/jsonschema-go@v0.3.0 contained the following incompatible bug fixes:
ForOptions.TypeSchemas
must be areflect.Type
, as incomparable values are not valid map keys.See #518 for a proposal to significantly decouple the SDK from the jsonschema-go package (though it would still be used for inference and validation). This decision blocks the v1.0.0 release.
New Contributors
Full Changelog: modelcontextprotocol/go-sdk@v0.6.0...v0.7.0
v0.6.0
Compare Source
This release makes a couple minor API tweaks that arose in preparation for v1.0.0, and adds significant feature documentation in the
docs/
directory.This is a release candidate, and all release blocking issues have now been addressed. We will tag v1.0.0 following a final audit (see also #328).
For more details, see the v0.6.0 milestone.
API Changes
StreamID
type, which was inconsistent with (for example) session IDs, which are strings (#484).GetSessionID
ontoServerOptions
, as that is more generally useful, and sinceServerSession
exposes anID
method (#478).Bug fixes
New Contributors
Full Changelog: modelcontextprotocol/go-sdk@v0.5.0...v0.6.0
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.