Bump hono from 4.12.23 to 4.12.31

[dependabot]

Bumps hono from 4.12.23 to 4.12.31.

Release notes

Sourced from hono's releases.

v4.12.31

What's Changed

• test(context): assert case-insensitive header names in response helpers by @​yusukebe in honojs/hono#5116
• chore(benchmark): add app.fetch() overhead benchmark by @​yusukebe in honojs/hono#5117
• refactor(aws-lambada): remove FIXME in @ts-expect-error by @​yusukebe in honojs/hono#5130
• fix(utils/body): reuse cached formData in parseBody() by @​yusukebe in honojs/hono#5131
• fix(request): fix multipart boundary mismatch in cloneRawRequest by @​yusukebe in honojs/hono#5133
• fix(sse): emit retry feild when retry is 0 by @​yusukebe in honojs/hono#5135
• test(validator): fix misspelled identifier in transform type test by @​yusukebe in honojs/hono#5136

Full Changelog: honojs/hono@v4.12.30...v4.12.31

v4.12.30

What's Changed

• chore(benchmark/routers): bump deps in honojs/hono#5107
• chore(benchmark): remove not used benchmarks in honojs/hono#5108
• chore: update to ts6 in prep for ts7 in honojs/hono#5104
• fix(cache): deduplicate Cache-Control directives case-insensitively in honojs/hono#5025
• fix(compress): do not compress 206 Partial Content responses in honojs/hono#5020
• fix(client): replaceUrlParam should not match a param that prefixes another in honojs/hono#5096
• fix(method-override): set duplex when forwarding a stream body in query mode in honojs/hono#5110

Full Changelog: honojs/hono@v4.12.29...v4.12.30

v4.12.29

What's Changed

• fix(client): merge function headers with per-request headers by @​yusukebe in honojs/hono#5092
• chore: fix no-op tsc in test script by @​yusukebe in honojs/hono#5093
• fix(lambda-edge): resolve the handler with the value passed to the callback by @​yusukebe in honojs/hono#5094
• docs(language): add JSDoc @​example to languageDetector by @​codebybilal18 in honojs/hono#5081
• test(workerd): add compatibilityDate by @​yusukebe in honojs/hono#5100
• fix(lambda-edge): base64 encode content-encoded response bodies by @​yusukebe in honojs/hono#5099
• fix(aws-lambda): treat any non-identity content-encoding as binary by @​yusukebe in honojs/hono#5101
• fix(types): strip extra properties from array types in JSONParsed by @​Arman-Luthra in honojs/hono#5103
• fix(trie-router): match empty wildcard remainder after regexp param by @​usualoma in honojs/hono#5102
• fix(etag): treat If-None-Match: * as a match by @​yusukebe in honojs/hono#5084

New Contributors

• @​codebybilal18 made their first contribution in honojs/hono#5081
• @​Arman-Luthra made their first contribution in honojs/hono#5103

Full Changelog: honojs/hono@v4.12.28...v4.12.29

v4.12.28

What's Changed

• fix(serve-static): treat empty string content as found by @​yusukebe in honojs/hono#5062
• docs(MIGRATION): fix req.raw.headers reference (property, not method) by @​EduardF1 in honojs/hono#5047
• chore: don't publish *.tsbuildinfo by @​yusukebe in honojs/hono#5066
• fix(utils/body,validator): normalize Content-Type media type for case-insensitive matching by @​yusukebe in honojs/hono#5067
• fix: avoid circular dependency between body.ts and request.ts by @​usualoma in honojs/hono#5071

... (truncated)

Commits

• cadff88 4.12.31
• 64c613a test(validator): fix misspelled identifier in transform type test (#5136)
• aeba9ec fix(sse): emit retry feild when retry is 0 (#5135)
• d796450 fix(request): fix multipart boundary mismatch in cloneRawRequest (#5133)
• 80959d4 fix(utils/body): reuse cached formData in parseBody() (#5131)
• 21b44b6 refactor(aws-lambada): remove FIXME in @ts-expect-error (#5130)
• 5f73897 docs(combine): close quote in combine JSDoc example (#5126)
• c285f9a chore(benchmark): add app.fetch() overhead benchmark (#5117)
• fb9d7bf test(context): assert case-insensitive header names in response helpers (#5116)
• b2ae3a2 4.12.30
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for hono since your current version.

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 rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will 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 version will 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 dependency will 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.

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm @sentry/node-core is 62.0% likely obfuscated Confidence: 0.62 Location: Package overview From: pnpm-lock.yaml → npm/react-scan@0.5.7 → npm/@sentry/node-core@10.67.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@sentry/node-core@10.67.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report