Skip to content

chore(node): accept @hono/node-server 1.x or 2.x #3084

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
felixweinberger merged 4 commits into from
Oct 23, 2026
+42 −27
Merged

chore(node): accept @hono/node-server 1.x or 2.x #3084

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
f22b26c
chore(node): accept @hono/node-server 1.x or 2.x
felixweinberger Oct 23, 2026
21b40a7
docs: let a runtime range span two majors in the dependency policy
felixweinberger Oct 23, 2026
a11abe7
Merge branch 'main' into chore/node-hono-node-server-range
felixweinberger Oct 23, 2026
ba512dd
Merge branch 'main' into chore/node-hono-node-server-range
felixweinberger Oct 23, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .changeset/node-hono-node-server-range.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
'@modelcontextprotocol/node': patch
---

The `@hono/node-server` dependency range widens from `^1.19.9` to `^1.19.9 || ^2.1.3`, so a new install resolves to 2.x and an install that cannot get 2.x keeps 1.x.
2 changes: 1 addition & 1 deletion DEPENDENCY_POLICY.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -30,6 +30,6 @@ Dependencies are only updated when there is a concrete reason, not simply becaus

## Pinning and Ranges

Ranges shared by more than one package live in the pnpm workspace catalogs (`pnpm-workspace.yaml`), so a version is declared once. Runtime dependencies use caret ranges (`^`) to allow compatible updates within a major version; exact versions of third-party runtime dependencies are pinned only when necessary to work around a specific issue. Dependencies between the SDK's own packages (`workspace:*`) publish as exact pins by design, so a released `client` or `server` always resolves the `core` it was built against. Framework integrations (`express`, `hono`, `fastify`) declare the framework as a peer dependency rather than bundling a copy.
Ranges shared by more than one package live in the pnpm workspace catalogs (`pnpm-workspace.yaml`), so a version is declared once. Runtime dependencies use caret ranges (`^`) to allow compatible updates within a major version, and a range may span two majors when the SDK works on both; exact versions of third-party runtime dependencies are pinned only when necessary to work around a specific issue. Dependencies between the SDK's own packages (`workspace:*`) publish as exact pins by design, so a released `client` or `server` always resolves the `core` it was built against. Framework integrations (`express`, `hono`, `fastify`) declare the framework as a peer dependency rather than bundling a copy.

Runtime dependencies of published packages are kept to a minimum; adding one is a significant change under the discuss-before-you-code rule in `CONTRIBUTING.md`.
60 changes: 35 additions & 25 deletions pnpm-lock.yaml
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion pnpm-workspace.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ catalogs:
eventsource-parser: ^3.0.8
jose: ^6.1.3
runtimeServerOnly:
'@hono/node-server': ^1.19.9
'@hono/node-server': ^1.19.9 || ^2.1.3
Comment thread
claude[bot] marked this conversation as resolved.
cors: ^2.8.5
express: ^5.2.1
fastify: ^5.2.0
Expand Down
Loading