Repository navigation
ci(typescript): bump hono from 4.13.13 to 4.13.19 - #6233
dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [hono](https://github.com/honojs/hono) from 4.13.13 to 4.13.19. - [Release notes](https://github.com/honojs/hono/releases) - [Commits](honojs/hono@v4.13.13...v4.13.19) --- updated-dependencies: - dependency-name: hono dependency-version: 4.13.19 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
strandly-the-agent
left a comment
There was a problem hiding this comment.
Verdict: Safe to merge: lockfile-only patch bump of a dev-only transitive package. Nothing we ship changes, and the only hono module our test tree loads is untouched by this range.
| Package | From → To | Tier | Scope |
|---|---|---|---|
hono |
4.13.13 → 4.13.19 | patch | dev, transitive (@modelcontextprotocol/sdk 1.32.2 and @modelcontextprotocol/node 2.1.2, via @hono/node-server 2.1.6); lockfile-only |
Breaking for this repo: None found. Nothing in the repo imports hono directly. It is reached only through the MCP test servers (strands-ts/test/integ/__fixtures__/test-mcp-server.ts:10, test-mcp-v2-server.ts:16), where @hono/node-server loads just hono/ws, which has no changes between these versions.
Tests: npm ci ✓ · npm run build ✓ · tsc --noEmit for src and test/integ ✓ 0 errors · vitest run --project unit-node src/mcp ✓ 241 passed · local MCP Streamable HTTP server/client round trip on hono 4.13.19 ✓ · skipped: integ (AWS-gated, waiting for approval on this PR).
Supply chain: one flag, checked: 4.13.19 was published 2026-11-16, about a day and a half before this review, so it is inside the repo's own 3-day patch cooldown (this arrived as a security update, which skips the cooldown). The npm provenance ties the tarball to honojs/hono tag v4.13.19, the lockfile hash matches the registry tarball, and there are no install scripts or dependencies. If you would rather let it age, the cooldown passes on 2026-11-19.
Details
- Why this PR exists. 4.13.13 is affected by five advisories published 2026-11-12, all fixed in 4.13.16: GHSA-46wx-v44x-9hh2 (
csrf()), GHSA-4h7h-rv7c-7m2v (validator('form')), GHSA-4m76-xfj5-7975 (mount()), GHSA-h7mg-cq63-vhpq (RegExpRouter), all moderate, and GHSA-3gg2-335m-rxc6 (csshelper, low). OSV lists none for 4.13.19. None of that code runs in our tree, so the practical effect here is clearing the alerts. - What changed, 4.13.14 to 4.13.19. Bug and security fixes in middleware, routers, JSX and helpers (
serve-static,csrf,mount,proxy,method-override,combine, RegExpRouter and TrieRouter), plus two additive options in 4.13.19 (secure-headersoverwrite,jwttyp).package.jsonchanges only the version:enginesstaysnode >=16.9.0and there are still no dependencies. One new internal module,utils/mount.js. - Reach. In
node_modules,honois imported by@hono/node-server(hono/wsfrom its index,hono/utils/mimefromserve-static) and by an example file inside@modelcontextprotocol/sdk. Our fixtures useStreamableHTTPServerTransportandtoNodeHandler, which import the@hono/node-serverindex only. - Supply-chain checks run. The SLSA attestation names workflow
.github/workflows/release.ymlatrefs/tags/v4.13.19, commit676c8f8, which is what the upstream tag points to. Provenance is present on 4.13.13 as well. I scanned the added lines of the 146-filenpm difffor new process, network, filesystem orevalcalls and found none. - Sources: hono releases v4.13.14 through v4.13.19 ·
npm diff --diff=hono@4.13.13 --diff=hono@4.13.19· npm registry metadata · OSV.
Bumps hono from 4.13.13 to 4.13.19.
Release notes
Sourced from hono's releases.
... (truncated)
Commits
676c8f84.13.199995a38feat(jwt): add a typ option to verify the token header (#5639)0e24cf6feat(secure-headers): add an overwrite option (#5634)ab74a8dfix(utils/types): stop JSONParsed at a recursive JSON type (#5645)399e7c9fix(lambda-edge): omit body in a 204 result (#5643)dea44c8fix(jsx/dom): keep a falsy Suspense fallback (#5644)2198388docs: fix JSDoc parameter types and missing annotations in middleware and hel...265f36bfix(combine): continue the chain when a Condition returns true in every() (#5...6dc11edfix(jsx/dom): restore attributes and effects when Suspense children suspend a...64a1d5afix(method-override): drop the body when overriding to GET or HEAD (#5641)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.