| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
🦋 Changeset detectedLatest commit: ea34a7d 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@2369
npm i https://pkg.pr.new/@modelcontextprotocol/codemod@2369
npm i https://pkg.pr.new/@modelcontextprotocol/core@2369
npm i https://pkg.pr.new/@modelcontextprotocol/server@2369
npm i https://pkg.pr.new/@modelcontextprotocol/server-legacy@2369
npm i https://pkg.pr.new/@modelcontextprotocol/express@2369
npm i https://pkg.pr.new/@modelcontextprotocol/fastify@2369
npm i https://pkg.pr.new/@modelcontextprotocol/hono@2369
npm i https://pkg.pr.new/@modelcontextprotocol/node@2369 commit: ea34a7d |
Sorry, something went wrong.
There was a problem hiding this comment.
SGTM
Sorry, something went wrong.
There was a problem hiding this comment.
Mostly wondering if we should be updating the elicitInput API given we want people to use inputRequired for MRTR going forward.
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Fixes #662.
Summary
The modern write-once handler works on 2026-07-28 natively and on 2025-era connections through the existing legacy input_required shim.
Release
Verification