chore(deps): bump hono from 4.12.28 to 4.12.34 in /.repos/effect-smol

[dependabot]

Bumps hono from 4.12.28 to 4.12.34.

Release notes

Sourced from hono's releases.

v4.12.34

Security fixes

This release includes fixes for the following security issues:

memo() retains SSR output across requests, leading to cross-user data disclosure

Affects: hono/jsx (server-side rendering). Fixes memo() reusing a retained render result across requests when props compare equal, where a component reading request-scoped values from ambient context — useContext(), useRequestContext(), or getContext() — could serve HTML rendered for another user's request, disclosing account data or request-scoped secrets such as CSRF tokens. GHSA-f23p-vx2j-j53r

ReDoS in CORS middleware via Access-Control-Request-Headers

Affects: hono/cors. Fixes a whitespace-tolerant regular expression with quadratic backtracking used to parse the Access-Control-Request-Headers preflight header when allowHeaders is not configured (the default), where a single preflight request carrying a long whitespace run could consume seconds of CPU and stall request processing. GHSA-8j4g-w8fx-2239

Algorithmic complexity DoS in Language Middleware

Affects: hono/language. Fixes quadratic string processing in language-tag normalization, where a crafted language tag with a large number of hyphen-separated subtags — supplied via a query parameter, cookie, or Accept-Language header — could cause excessive CPU consumption and block the event loop. GHSA-54fx-42gc-7vw4

Proxy Helper does not remove response headers listed in the Connection header

Affects: hono/proxy. Fixes proxy() forwarding response headers that the origin's Connection header designates as connection-scoped, where headers intended only for the immediate peer — per RFC 9110 Section 7.6.1 — could be exposed to clients, disclosing connection-scoped or internal metadata. GHSA-79qm-7rj5-m7r9

---

Users who use hono/jsx for server-side rendering, hono/cors, hono/language, or hono/proxy are strongly encouraged to upgrade to this version.

v4.12.33

What's Changed

• fix(cookie): relax name validation when parsing Cookie header in honojs/hono#5164
• chore: bump @hono/node-server in honojs/hono#5167
• fix(jsx): handle useSyncExternalStore subscription and snapshot changes in honojs/hono#5166
• chore: remove undici in favor of global fetch in honojs/hono#5168

Full Changelog: honojs/hono@v4.12.32...v4.12.33

v4.12.32

What's Changed

• ci: enable reports for type & bundle size check in honojs/hono#5148
• fix(aws-lambda): add jwt and lambda authorizer types for API Gateway v2 in honojs/hono#5142
• fix(sse): emit empty id field to reset Last-Event-ID in honojs/hono#5138
• test(cloudflare-workers): add coverage for onClose, onError, send, and close in Cloudflare Workers websocket adapter in honojs/hono#5145
• fix: use Object.create(null) when parsing query, headers, and params in honojs/hono#5161
• fix(secure-headers): keep CSP callbacks scoped to their header in honojs/hono#5147

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

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

... (truncated)

Commits

• 734755a 4.12.34
• 9839ff3 chore: update bun.lock (#5182)
• 0c45036 Merge commit from fork
• 720b566 Merge commit from fork
• f70e2c3 Merge commit from fork
• 93fc250 Merge commit from fork
• 51db313 4.12.33
• aed1463 chore: remove undici in favor of global fetch (#5168)
• 224d2f5 fix(jsx): handle useSyncExternalStore subscription and snapshot changes (#5166)
• df653ce chore: bump @hono/node-server (#5167)
• Additional commits viewable in compare view

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.

[radroid]

Closing — this is noise, not a fix, and merging it would cost us on every sync.

.repos/effect-smol is a vendored reference subtree, not a workspace package:

• It is not matched by any glob in pnpm-workspace.yaml (apps/*, infra/*, oxlint-plugin-t3code, packages/*, scripts), so nothing here is ever installed, bundled or shipped. The advisory is not reachable from any artifact we build.
• ci.yml explicitly sparse-checks-out !/.repos/ — the code in this PR is not even present when CI runs.
• It is maintained by scripts/sync-reference-repos.ts as a git subtree pulled from the real upstream (added in chore: add vendored reference repo subtree sync tooling pingdotgg/t3code#2902 / chore: add Alchemy reference repo subtree pingdotgg/t3code#2918). A fork-local edit to a file inside the subtree diverges it from its source, so the next subtree pull conflicts — and the conflict lands in a ~30k-line lockfile.
• It sits inside the daily rebase-onto-upstream path, so the same hunk would be re-conflicted on every upstream sync.

The right place to fix this advisory is effect-smol upstream; it reaches us for free on the next subtree pull.

.github/dependabot.yml now ignores the vendored directories so this stops recurring.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.