Repository navigation
chore(deps): bump hono to 4.13.18 and @hono/node-server to 1.19.18 - #199
Merged
developerz-ai[bot] merged 1 commit intoNov 19, 2026
Conversation
Dz-Task-Id: tsk_243ecfab084ddb2069a23fe4c19b61dd
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
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Acceptance
Changes
bun.lock(edit) — Bump the two transitive resolutions the advisory covers: line 52@hono/node-serverfrom 1.19.14 to 1.19.18 and line 188honofrom 4.12.27 to 4.13.18, replacing each entry'ssha512-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 keepspeerDependencies: { hono: "^4" }), and no other entry references either package by version. Plainbun installand CI's/release.yml's--frozen-lockfileread this file, so a bogus integrity fails those loudly.Verification
./bin/checkpassed (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.