Repository navigation
Comparing changes
Open a pull request
base repository: honojs/hono
base: v4.12.19
head repository: honojs/hono
compare: v4.12.23
- 20 commits
- 31 files changed
- 12 contributors
Commits on May 19, 2026
-
Configuration menu - View commit details
-
Copy full SHA for dcabbec - Browse repository at this point
Copy the full SHA dcabbecView commit details -
Configuration menu - View commit details
-
Copy full SHA for eb2d0c2 - Browse repository at this point
Copy the full SHA eb2d0c2View commit details -
Configuration menu - View commit details
-
Copy full SHA for c657a39 - Browse repository at this point
Copy the full SHA c657a39View commit details -
Configuration menu - View commit details
-
Copy full SHA for 5463db2 - Browse repository at this point
Copy the full SHA 5463db2View commit details -
Configuration menu - View commit details
-
Copy full SHA for 905aedb - Browse repository at this point
Copy the full SHA 905aedbView commit details -
* fix(ip-restriction): match static IP rules numerically * fix: throw TypeError for invalid IP addresses in ipaddr utils * fix(ip-restriction): validate CIDR prefixes
Configuration menu - View commit details
-
Copy full SHA for c831020 - Browse repository at this point
Copy the full SHA c831020View commit details -
Configuration menu - View commit details
-
Copy full SHA for 6cbb025 - Browse repository at this point
Copy the full SHA 6cbb025View commit details -
Configuration menu - View commit details
-
Copy full SHA for a83ddb8 - Browse repository at this point
Copy the full SHA a83ddb8View commit details
Commits on May 22, 2026
-
chore: update vitest to v4 and cleanups (#4952)
* chore: update vitest to v4 and cleanups * ci: apply automated fixes * fix: vitest jsx import --------- Co-authored-by: autofix-ci[bot] <114827586+autofix-ci[bot]@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for cf6ef70 - Browse repository at this point
Copy the full SHA cf6ef70View commit details -
fix(mime): specify charset parameter per MIME type instead of mechani…
…cal detection (#4912) Per #4510: - Inline `; charset=utf-8` in `_baseMimes` for all text/* entries plus `image/svg+xml`, `application/xhtml+xml`, and `application/xml`, which are XML-based formats that benefit from an explicit charset. - Drop the `if (mimeType.startsWith("text"))` block in `getMimeType`; the charset now lives in the data, not in the lookup logic. Output for text types is unchanged (still "text/<sub>; charset=utf-8"). - Update `getExtension` to compare the base type (the part before the first `;`), so callers can pass either a raw type ("text/html") or one with parameters ("text/html; charset=utf-8") and still get the correct extension back. Tests: 5 mime.test.ts cases pass (3 existing + 2 new) covering the new charset values for svg/xhtml/xml/ics/mjs/css/csv and getExtension with parameters. Closes #4510
Configuration menu - View commit details
-
Copy full SHA for a192df0 - Browse repository at this point
Copy the full SHA a192df0View commit details -
fix(compress): respect Accept-Encoding when encoding option is set (#…
…4951) * fix(compress): skip compression when client does not accept the configured encoding When the encoding option is set, the middleware previously compressed responses unconditionally, regardless of the Accept-Encoding header. This could send a response in an encoding the client cannot decode (for example, returning gzip when the client only advertised deflate, or when Accept-Encoding is absent). Honor the client's Accept-Encoding header even when an encoding is explicitly configured, falling back to no compression when the configured encoding is not accepted. * fix(compress): use parseAccept to honor q-values, wildcard, and case Address review from @yusukebe. The previous version used String.includes on the raw Accept-Encoding header, which treated x-gzip as gzip, ignored q=0 explicit refusals, and did not understand the wildcard. Switch to parseAccept (already used by accepts middleware) and pick the candidate encoding with the highest non-zero q value, falling back to the wildcard q if the candidate has no explicit entry. Add seven regression tests covering q=0 on the configured encoding, q=0 fallback to another candidate, wildcard \*, case-insensitive tokens, x-gzip non-matching, highest-q wins, and gzip-over-deflate tie-break. * fix(compress): short-circuit selectEncoding when q is 1 Per @usualoma: q values are almost always 1 in practice, so short-circuit and return immediately for the common path instead of continuing to scan the remaining candidates. Co-authored-by: Yusuke Wada <[email protected]> Co-authored-by: Taku Amano <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for f0ed246 - Browse repository at this point
Copy the full SHA f0ed246View commit details -
fix(deno): echo negotiated WebSocket subprotocol in upgrade response (#…
…4955) * fix(deno): echo negotiated WebSocket subprotocol in upgrade response The Deno adapter did not set the `Sec-WebSocket-Protocol` header on the upgrade response, so browsers such as Chrome rejected connections that requested a subprotocol. Read the first value from the request's `Sec-WebSocket-Protocol` header and pass it as the `protocol` option to `Deno.upgradeWebSocket`, while still honoring an explicitly provided `protocol` option. Closes #4439 * add a test --------- Co-authored-by: ATOM00blue <[email protected]> Co-authored-by: Yusuke Wada <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 7e0555d - Browse repository at this point
Copy the full SHA 7e0555dView commit details -
Configuration menu - View commit details
-
Copy full SHA for 6bc0dff - Browse repository at this point
Copy the full SHA 6bc0dffView commit details -
Configuration menu - View commit details
-
Copy full SHA for 2f01b77 - Browse repository at this point
Copy the full SHA 2f01b77View commit details
Commits on May 24, 2026
-
fix(serve-static): normalize all backslashes in file paths, not just …
…the first (#4962) `getFilePathWithoutDefaultDocument` converts backslash separators to slashes so the same path resolves consistently regardless of the separator style of the incoming request. The replace used a non-global regex (`/\/`), so only the FIRST backslash was converted: a path with multiple segments like `foo\bar\baz.txt` became `foo/bar\baz.txt` — mixed separators that resolve to the wrong file (or 404) on platforms that don't treat `\` as a separator. The adjacent comment (`foo\bar.txt => foo/bar.txt`) shows the intent was to normalize all of them. Fix: add the `g` flag (`/\/g`). Behaviour is unchanged for any path with zero or one backslash, so all existing tests pass; added a regression test covering a multi-segment path (with and without `root`) that returns the broken `foo/bar\baz.txt` before this change. tsc --noEmit clean; eslint + prettier clean. Co-authored-by: Prodia Evolution Worker <[email protected]>
francisjohnjohnston-web and Prodia Evolution Worker authoredMay 24, 2026 Configuration menu - View commit details
-
Copy full SHA for 82dad62 - Browse repository at this point
Copy the full SHA 82dad62View commit details -
Configuration menu - View commit details
-
Copy full SHA for c84c5d2 - Browse repository at this point
Copy the full SHA c84c5d2View commit details -
Configuration menu - View commit details
-
Copy full SHA for 0265a54 - Browse repository at this point
Copy the full SHA 0265a54View commit details
Commits on May 25, 2026
-
feat(compress): add contentTypeFilter option and `COMPRESSIBLE_CONTEN…
…T_TYPE_REGEX` re-export (#4961) Co-authored-by: Taku Amano <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for c968177 - Browse repository at this point
Copy the full SHA c968177View commit details -
fix(utils/ipaddr): do not compress a single 0 group to
::(#4971)Co-authored-by: Taku Amano <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for bcd290a - Browse repository at this point
Copy the full SHA bcd290aView commit details -
Configuration menu - View commit details
-
Copy full SHA for 83bfb3b - Browse repository at this point
Copy the full SHA 83bfb3bView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v4.12.19...v4.12.23