chore(repo): version packages - #324
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
Contributor
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 19, 2026 15:32
b774053 to
f0d530c
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
nitro-mcp-toolkit@0.3.0
Minor Changes
#323
936679eThanks @HugoRCD! - The runtime is now h3-mcp 0.2.0.defineMcp*still wrap plain returns and turn a throw intoisError; transport, eras, auth, origin, MRTR, and subscriptions come from the engine.This is a breaking change on 0.x:
ResourceTemplate/completableare gone. A template isuriTemplateplus optionallist/complete; prompt completions live onarguments.inputRequired/mcpElicit/getElicitedContent/defineRequestStatereplaceinputResponse/acceptedContent.legacy/responseModebecomeera(dualis the default,modernis 2026-07-28 only).event.context.mcp.mcpReq/authare gone. ReadinputResponses,requestState,signal, anderaoff the engine context.handler.fetch(req, { authInfo })is gone; sendAuthorizationorx-api-key.handler.bus/handler.closeare gone.handler.notifystill fans out to every listener.nodejs_compat.X-MCP-Toolsheader naming an unknown tool is a 400 only after origin and auth have passed, so the name does not leak to a caller who is not allowed through.createMcpHandlertakes h3-mcp's{ extensionPlugins }as a second argument, for tasks and MCP Apps.AuthOptions,CacheHints,CallToolResult,Era,PluginOptions, …) keep their h3-mcp names.getInputResponses/getMissingInputs/canRequestInput/getSupportedInputs/McpJsonRpcErrorare re-exported so a handler does not need a second import fromh3-mcp.nitrois an optional peer: it is only required fornitro-mcp-toolkit/module.createMcpHandlerneedsh3.createMcpTestClientaccepts{ headers }so a Bearer token orX-MCP-Toolsallowlist does not need a customfetchwrap.{ mcp }(or{ adminMcp }for/admin/mcp) fromnitro-mcp-toolkit/servers.#mcp/<slug>/handleris still what Nitro mounts, not what an app imports.