Repository navigation
chore(deps): update hono - #106
Merged
Merged
Conversation
renovate
Bot
force-pushed
the
renovate/hono
branch
3 times, most recently
from
November 18, 2026 09:54
2af1d43 to
685814b
Compare
renovate
Bot
force-pushed
the
renovate/hono
branch
from
November 21, 2026 10:05
685814b to
ac42bc9
Compare
Contributor
Author
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
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.
This PR contains the following updates:
2.1.6→2.1.114.13.16→4.13.19Release Notes
honojs/node-server (@hono/node-server)
v2.1.11Compare Source
Security fix
Unhandled
ECONNRESETon a non-WebSocketUpgraderequest crashes the process when WebSocket support is enabledAffects: applications that use the
websocketoption. A request with anUpgradeheader other thanwebsocketleft the socket without an error listener. A client that reset the connection at that point crashed the process. Version 2.1.10 closed the leak for these requests but a reset that arrived before the400response was written still crashed. GHSA-qhm2-7mpr-ghjpThe error listener is now attached as soon as the socket is handed to the upgrade listener.
Full Changelog: honojs/node-server@v2.1.10...v2.1.11
v2.1.10Compare Source
Security fix
WebSocket upgrade listener leaves non-WebSocket
Upgraderequests open, leading to socket exhaustionAffects: applications that use the
websocketoption. The upgrade listener ignored requests whoseUpgradeheader was notwebsocket, so the socket stayed open until the client closed it. A client could hold many connections open this way, and clients that try an HTTP/2 upgrade over plain HTTP hung. GHSA-8wcc-wqxr-28qpSuch a request is now answered with
400 Bad Requestand the socket is closed, unless the application registers its ownupgradelistener.Full Changelog: honojs/node-server@v2.1.9...v2.1.10
v2.1.9Compare Source
What's Changed
Full Changelog: honojs/node-server@v2.1.8...v2.1.9
v2.1.8Compare Source
What's Changed
Full Changelog: honojs/node-server@v2.1.7...v2.1.8
v2.1.7Compare Source
Security fixes
This release includes a fix for the following security issue:
serveStaticwithallowPercentInPathstill allows the double-decode middleware bypassAffects:
serveStaticwithallowPercentInPath: true. The fix for GHSA-rmxm-3fg6-px4f rejects a path containing%, but theallowPercentInPathoption skipped that check entirely. A malformed percent sequence such as/static/%%36%31dmin/secret.txtwas routed as/static/%61dmin/secret.txt, so middleware on/static/admin/*did not run, andserveStaticthen decoded%61toaand servedstatic/admin/secret.txt. The default configuration was already fixed in 2.1.3. GHSA-fj57-4f93-cfw6serveStaticnow accepts the second decode only when its result equals the routed path with%25replaced by%. File names containing a literal%, requested as%25, are served as before.The same fix ships in
honov4.13.18 (GHSA-74fm-fwc7-3fwp).Full Changelog: honojs/node-server@v2.1.6...v2.1.7
honojs/hono (hono)
v4.13.19Compare Source
What's Changed
Full Changelog: honojs/hono@v4.13.18...v4.13.19
v4.13.18Compare Source
Security fixes
This release includes fixes for the following security issues:
validator()skips validation for requests whoseContent-Typeparameters are formatted differentlyAffects:
validator('json')andvalidator('form')inhono/validator. AContent-Typewith whitespace before;, a trailing;, or an unusual parameter name was not recognized, so the validator saw an empty object while the handler could read all fields. This completes the fix for GHSA-4h7h-rv7c-7m2v. The validator now decides by the media type alone, asc.req.parseBody()does. GHSA-92p4-j3wq-jmqxbodyLimit()keeps every transfer chunk of a request body in memoryAffects:
bodyLimit()inhono/body-limit. A body sent in very small transfer chunks was retained as one object per chunk, so a request within the configured limit could exhaust memory. The body is now buffered in one array bounded bymaxSize. GHSA-39q9-qp46-w8xgmount()andapp.mount()forward a wrong path when a customgetPathadds a prefixAffects:
mount()inhono/mountandapp.mount()on 4.13.16 and 4.13.17. With agetPaththat prepends a prefix such as the host name, one segment too many was removed from the forwarded path, so middleware scoped inside the mount prefix could be skipped. The prefix is removed from the routed path again. Paths that would change meaning when forwarded now get 400, and an optional regular expression parameter in a mount path throws. GHSA-h25j-2p75-qj33serveStatic()serves a path that was decoded twice whenallowPercentInPathis enabledAffects:
serveStatic()inhono/serve-staticand the runtime adapters, only withallowPercentInPath: true. A malformed percent escape in the request path was decoded a second time, so a path that middleware registered on the encoded form did not see could still reach a static file. The file path must now be the same as the routed path, and otherwise the response is 404. GHSA-74fm-fwc7-3fwpUsers who rely on
validator(),bodyLimit(),mount()with a customgetPath, orserveStatic()withallowPercentInPathare strongly encouraged to upgrade to this version.Full Changelog: honojs/hono@v4.13.17...v4.13.18
v4.13.17Compare Source
What's Changed
__Secure-and__Host-prefixes case-insensitively in #5608setMetricin #5363__Secure-and__Host-prefixes case-insensitively inCookieConstraintin #5611ErrorBoundaryin #5430toSSGruns in #5381Full Changelog: honojs/hono@v4.13.16...v4.13.17
Configuration
📅 Schedule: (in timezone America/Los_Angeles)
* * * * 4)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.