Skip to content

Conversation

@github-actions
Copy link

@github-actions github-actions bot commented Nov 8, 2025

This PR updates src/spec.types.ts from the Model Context Protocol specification.

Source file: https://github.com/modelcontextprotocol/modelcontextprotocol/blob/970851ea5cbd31c52b0579cea6483a884ca5eb74/schema/draft/schema.ts

This is an automated update triggered by the nightly cron job.

@github-actions github-actions bot requested a review from a team as a code owner November 8, 2025 04:04
@github-actions github-actions bot force-pushed the update-spec-types branch 4 times, most recently from bc1d786 to cc1ab1c Compare November 13, 2025 04:07
@felixweinberger felixweinberger added the improves spec compliance When a change improves ability of SDK users to comply with spec definition label Nov 13, 2025
@pkg-pr-new
Copy link

pkg-pr-new bot commented Nov 14, 2025

Open in StackBlitz

npm i https://pkg.pr.new/modelcontextprotocol/typescript-sdk/@modelcontextprotocol/sdk@1092

commit: cd52576

@felixweinberger
Copy link
Contributor

Outdated, will defer to the next nightly run.

@pcarleton
Copy link
Member

I think the flow is to update this PR, even if it's closed, which might be broken:

Run git config user.name "github-actions[bot]"
Switched to a new branch 'update-spec-types'
M	src/spec.types.ts
[update-spec-types a9929e9] chore: update spec.types.ts from upstream
 1 file changed, 354 insertions(+), 15 deletions(-)
To https://github.com/modelcontextprotocol/typescript-sdk
 + 7fe1d89...a9929e9 update-spec-types -> update-spec-types (forced update)
PR already exists, updating description...
https://github.com/modelcontextprotocol/typescript-sdk/pull/1092

https://github.com/modelcontextprotocol/typescript-sdk/actions/runs/19580790717/job/56077911880

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

improves spec compliance When a change improves ability of SDK users to comply with spec definition

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants