| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
🦋 Changeset detectedLatest commit: 1b4079e The changes in this PR will be included in the next version bump. This PR includes changesets to release 6 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Sorry, something went wrong.
|
@modelcontextprotocol/client
npm i https://pkg.pr.new/@modelcontextprotocol/client@2481
npm i https://pkg.pr.new/@modelcontextprotocol/codemod@2481
npm i https://pkg.pr.new/@modelcontextprotocol/core@2481
npm i https://pkg.pr.new/@modelcontextprotocol/server@2481
npm i https://pkg.pr.new/@modelcontextprotocol/server-legacy@2481
npm i https://pkg.pr.new/@modelcontextprotocol/express@2481
npm i https://pkg.pr.new/@modelcontextprotocol/fastify@2481
npm i https://pkg.pr.new/@modelcontextprotocol/hono@2481
npm i https://pkg.pr.new/@modelcontextprotocol/node@2481 commit: 1b4079e |
Sorry, something went wrong.
|
Rebased onto current main. Revalidated the touched packages: core-internal media-type tests 11/11 pass, server streamable HTTP tests 55/55 pass, and both package typechecks are clean. The repository pre-push hook also completed the full workspace build, lint, and typecheck successfully. CI is rerunning now. |
Sorry, something went wrong.
|
@felixweinberger, when you have a chance, could you review this? It complements #2441 by applying exact media-type parsing to Accept; the branch is rebased onto current main, mergeable, and all CI checks are green. |
Sorry, something went wrong.
Reject Streamable HTTP requests whose Accept values only contain the required media types as substrings, while preserving case-insensitive and parameterized values. Adds GET/POST regression coverage. Fixes modelcontextprotocol#2480. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Rebased again onto current main (head bf3bfcb). The branch is mergeable and no longer behind; all 14 checks are green, including build, examples E2E, Node 20/22/24 unit and E2E suites, Bun/Deno runtime tests, and client/server conformance. @felixweinberger, when you have bandwidth, could you review this focused Accept media-type parsing fix? |
Sorry, something went wrong.
|
Merged current main (70de0c8b) into the branch; the PR is mergeable and no longer behind. The latest head also respects RFC 9110 quality exclusions: a required media type with q=0 is not treated as supported, while positive quality values remain accepted. All 14 checks are green at head 1b4079e6, including Node 20/22/24 unit and E2E suites, Bun/Deno runtime tests, client/server conformance, build, examples E2E, and continuous package publishing. The focused current-head suites also pass locally: core-internal media-type tests 12/12 and server Streamable HTTP tests 61/61. The corresponding v1.x backport is ready as draft #2738, with all applicable CI checks green. @felixweinberger, this is the remaining Accept-header counterpart to the parsed Content-Type validation from #2441/#2444. Could you review when available? |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Fixes #2480.
Summary
Streamable HTTP server Accept validation used raw substring checks, so values such as application/jsonx and text/event-stream-bogus incorrectly satisfied the required concrete media types. This affected both POST negotiation and GET SSE requests.
This change:
This follows the same parsed-media-type approach recently applied to Content-Type in #2441 / #2444, while keeping Accept-specific list parsing internal.
Testing
Validated after merging current main (70de0c8b):
The remaining platform-local check:all docs step is covered by CI; TypeDoc rejects native Windows backslash entry-point globs before documentation generation.