chore(deps): bump hono from 4.11.4 to 4.12.7

[tiluckdave]

Motivation and Context

hono@4.11.4 has 9 known vulnerabilities (1 high, 7 moderate, 1 low) including arbitrary file access via serveStatic (CVE-2026-29045), cookie attribute injection (CVE-2026-29086), prototype pollution in parseBody, SSE control field injection, and others. 4.12.7 is the minimum version that clears all of them.

How Has This Been Tested?

• Ran pnpm test:all everything clean.
• Confirmed hono@4.12.7 has no known vulnerabilities via OSV

Breaking Changes

None.

Types of changes

• Bug fix (non-breaking change which fixes an issue)

Checklist

• I have read the MCP Documentation
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have added or updated documentation as needed

[changeset-bot]

⚠️ No Changeset found

Latest commit: d26bf7b

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[pkg-pr-new]

Open in StackBlitz

@modelcontextprotocol/client

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

@modelcontextprotocol/server

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

@modelcontextprotocol/express

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

@modelcontextprotocol/hono

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

@modelcontextprotocol/node

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

commit: d26bf7b

[felixweinberger]

Thanks for flagging the CVEs. Hono is a peer dependency though, so consumers bring their own version and npm audit / dependabot will flag these on their end. We keep peer dep minimums loose unless the SDK itself needs a newer API. Closing.