Skip to content

chore(deps): bump hono to 4.13.18 and @hono/node-server to 1.19.18 - #199

Merged
developerz-ai[bot] merged 1 commit into
mainfrom
dz/raise-hono-to-4-13-18-and-hono-node-server-to-1--243ecfab
Nov 19, 2026
Merged

developerz-ai[bot] merged 1 commit into
mainfrom
dz/raise-hono-to-4-13-18-and-hono-node-server-to-1--243ecfab

Conversation

@developerz-ai

@developerz-ai developerz-ai Bot commented Nov 19, 2026 •

Copy link
Copy Markdown
Contributor

Acceptance

  • bun.lock resolves hono@4.13.18 and @hono/node-server@1.19.18, each with the registry integrity hash for that version
  • No entry in bun.lock names hono@4.12.27 or @hono/node-server@1.19.14 (grep finds neither string)
  • bun install --frozen-lockfile succeeds: the lock still parses and satisfies @modelcontextprotocol/sdk's declared ranges (hono ^4.11.4, @hono/node-server ^1.19.9 || ^2.0.5) and package.json is unchanged
  • The named advisory ranges no longer match: resolved hono 4.13.18 >= 4.13.18 and @hono/node-server 1.19.18 >= 1.19.18
  • ./bin/check stays green (typecheck, lint, SKIP_BROWSER_INTEGRATION=1 bun test) — no source file references hono directly, so only the lock's own consumers are affected

Changes

  • bun.lock (edit) — Bump the two transitive resolutions the advisory covers: line 52 @hono/node-server from 1.19.14 to 1.19.18 and line 188 hono from 4.12.27 to 4.13.18, replacing each entry's sha512- integrity with the registry value for the new version. Nothing else in the file changes: both entries keep "" and their deps/peer maps (hono has no dependencies; @hono/node-server keeps peerDependencies: { hono: "^4" }), and no other entry references either package by version. Plain bun install and CI's/release.yml's --frozen-lockfile read this file, so a bogus integrity fails those loudly.

Verification

./bin/check passed (exit 0) in 1m 11s.

What the editors ran to see the change working, and what they saw:

  • curl -s https://registry.npmjs.org/hono/4.13.18 and https://registry.npmjs.org/@hono/node-server/1.19.18 (deps): dist.integrity for hono@4.13.18 is sha512-H9q/E1XizaWstJxUW881dmLxEj+t/TrGGnyxINkm4+[REDACTED:high_entropy]== (engines node >=16.9.0); for @hono/node-server@1.19.18 sha512-609kppIP9GITS+[REDACTED:high_entropy]/XYtlogqmrLchDv5HX5w== with peerDependencies {hono: ^4} and engines node >=18.14.1 — both hashes written into the lock match these verbatim.
  • node -e 'JSON.parse(bun.lock with trailing commas stripped)' after the edit (deps): parsed cleanly: packages["hono"] = ["hono@4.13.18", "", {}, "sha512-H9q/E1XizaWstJxUW881dmLxEj+t/TrGGnyxINkm4+[REDACTED:high_entropy]=="], packages["@hono/node-server"] = ["@hono/node-server@1.19.18", "", {"peerDependencies":{"hono":"^4"}}, "sha512-609kppIP9GITS+...=="], count 140 — same shape, only the two version/integrity pairs changed.
  • code_grep '1\.19\.14|4\.12\.27' bun.lock and code_changes bun.lock (deps): zero hits for the old versions (the only remaining hono/@HONO mentions are the sdk's dependency-range line 54, unchanged); diff is two lines, one per package.

Raised automatically by a developerz.ai maintainer lane.

Dispatched automatically by a developerz.ai maintainer lane
Raised automatically by the developerz.ai raw task triage maintainer lane, from manual.
Plan: https://app.developerz.ai/fleet/plans/rtk_e22527043e4244c987621129c745b9a4
Part 1/1
BYOK spend: $0.02 reported by the provider (byok funding evidence).

Dz-Task-Id: tsk_243ecfab084ddb2069a23fe4c19b61dd
@developerz-ai developerz-ai Bot added the dz/fleet-pr Opened by the developerz.ai maintainer bot from a fleet run. label Nov 19, 2026
@developerz-ai
developerz-ai Bot merged commit 5e02bb2 into main Nov 19, 2026
3 checks passed
@developerz-ai
developerz-ai Bot deleted the dz/raise-hono-to-4-13-18-and-hono-node-server-to-1--243ecfab branch November 19, 2026 00:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dz/fleet-pr Opened by the developerz.ai maintainer bot from a fleet run.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants