Skip to content

Drop redundant @hono/node-server override, document SSE keep-alive - #67

Merged
SVilgelm merged 3 commits into
mainfrom
sdk-1.30-cleanup
Aug 9, 2026
Merged

Drop redundant @hono/node-server override, document SSE keep-alive#67
SVilgelm merged 3 commits into
mainfrom
sdk-1.30-cleanup

Conversation

@SVilgelm

@SVilgelm SVilgelm commented Aug 9, 2026

Copy link
Copy Markdown
Member

MCP SDK 1.30.0 widened its own @hono/node-server range to ^1.19.9 || ^2.0.5, which is what our override was working around. Regenerating the lockfile without the override produces a byte-identical package-lock.json (still resolves 2.0.12), so removing it changes nothing today and stops us silently pinning the dependency if upstream moves again.

The same SDK release turned on SSE keep-alive comment frames (15s) and started setting X-Accel-Buffering: no / Cache-Control: no-transform on SSE responses. We get both for free, but only because http-bridge.ts is byte- and header-transparent, so I documented them in CLAUDE.md as constraints on that file rather than as trivia: readableStreamToBufferGenerator may only drop zero-length chunks, and fromWebResponse must keep copying the full header set. This matters most for the long-idle streams — create_backup on a large database, and the restore_backup elicitation round-trip that idles until a human answers.

Also noted that request Content-Type is now validated by parsed media type instead of substring match.

The second commit clears npm audit. Three of our overrides had drifted into pinning the vulnerable ceiling of an advisory rather than protecting against it: fast-uri ^3.1.4 -> ^3.1.5 (GHSA-7p8r-x3mc-p8w7 covers 3.0.0-3.1.4), hono ^4.12.27 -> ^4.12.34 (four advisories cover <=4.12.33), and brace-expansion ^5.0.8 -> ^5.0.9 (GHSA-rgw5-rvv9-x895 covers 4.0.0-5.0.8). fast-uri stays on 3.x deliberately — ajv requires ^3.0.1, so a 4.x override would be out of range. Audit is now clean, and fmt:check, lint and build all pass against the reinstalled tree.

MCP SDK 1.30.0 widened its own @hono/node-server range to
^1.19.9 || ^2.0.5, so the override no longer changes resolution
(package-lock.json is byte-identical without it).

Assisted-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Signed-off-by: Sergey Vilgelm <sergey@vilgelm.com>
Copilot AI lite review requested due to automatic review settings August 9, 2026 01:06

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

Each of these overrides pinned to a version that has since become
the vulnerable ceiling of an advisory:

- fast-uri ^3.1.4 -> ^3.1.5 (GHSA-7p8r-x3mc-p8w7, affects 3.0.0-3.1.4).
  Kept on 3.x: ajv requires ^3.0.1, so a 4.x override would be out of range.
- hono ^4.12.27 -> ^4.12.34 (four advisories affecting <=4.12.33).
- brace-expansion ^5.0.8 -> ^5.0.9 (GHSA-rgw5-rvv9-x895, affects 4.0.0-5.0.8).

npm audit is now clean. fmt:check, lint and build pass.

Assisted-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Signed-off-by: Sergey Vilgelm <sergey@vilgelm.com>
Copilot AI review requested due to automatic review settings August 9, 2026 01:09

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

main #66 fixed the same three advisories independently. Conflict was
on the hono override only: kept ^4.12.34 over main's ^4.12.27 so the
pin encodes the advisory floor (<=4.12.33 is vulnerable) rather than
relying on resolution alone. Lockfile regenerated; npm audit clean.

Assisted-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Signed-off-by: Sergey Vilgelm <sergey@vilgelm.com>
@SVilgelm
SVilgelm merged commit 5b71aa5 into main Aug 9, 2026
5 checks passed
@SVilgelm
SVilgelm deleted the sdk-1.30-cleanup branch August 9, 2026 01:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants