chore(deps): bump hono from 4.12.28 to 4.13.7 in /app

[dependabot]

Bumps hono from 4.12.28 to 4.13.7.

Release notes

Sourced from hono's releases.

v4.13.7

Security fixes

This release includes a fix for the following security issue:

hono/jsx renders plain strings unescaped in boundary components, leading to XSS

Affects: Suspense, ErrorBoundary, and Context.Provider in hono/jsx, and renderToString() / renderToReadableStream() in hono/jsx/dom/server. Fixes missing HTML escaping for a plain string placed directly as a child or fallback of these components, or as the root value of the server rendering functions, so untrusted strings could be emitted as markup. GHSA-hxh3-vqpv-xpqv

---

Users who render untrusted strings inside Suspense, ErrorBoundary, or Context.Provider, or pass them directly to hono/jsx/dom/server, are strongly encouraged to upgrade to this version.

v4.13.6

What's Changed

• fix(client): keep a param value of "index" in $url() and $path() in honojs/hono#5297
• fix(client): normalize root WebSocket URLs in honojs/hono#5291
• fix(types): allow symbol keys in Context get and set fallbacks in honojs/hono#5300
• chore: bump editorconfig-checker in honojs/hono#5336
• refactor(on-handler): use forEach for consistent handler iteration in honojs/hono#5326

Full Changelog: honojs/hono@v4.13.5...v4.13.6

v4.13.5

Security fixes

This release includes fixes for the following security issues:

Query parser reads parameters after the URL fragment, causing cache-key and proxy interpretation differentials

Affects: Cache Middleware and applications behind a proxy, WAF, or logging layer that inspects query strings. Fixes query parsing that did not stop at the URL fragment, so a ? after a # was treated as the start of a query string and the application could read parameters that the other component never saw. GHSA-crvj-82cr-hjcx

Incomplete fix for CVE-2026-39408: toSSG() still writes files outside the output directory

Affects: toSSG() for Static Site Generation. Fixes a path normalization gap where consecutive parent-directory segments in ssgParams values were not fully collapsed, bypassing the containment check added in 4.12.12. GHSA-gqvv-2mrq-wpjv

Unbounded dot-notation nesting in parseBody() can cause memory exhaustion

Affects: parseBody() when dot-notation parsing is enabled. Fixes unbounded expansion of dot-separated field names, where a small request body could allocate a disproportionately large object graph and concurrent requests could exhaust the heap. GHSA-g6gw-c38x-mqfc

---

Users who use Cache Middleware, deploy behind a proxy or WAF that inspects query strings, use Static Site Generation, or use parseBody({ dot: true }) are strongly encouraged to upgrade to this version.

v4.13.4

What's Changed

• fix(request): handle params on unmatched requests in honojs/hono#5268
• fix(jsx/dom): execute previous ref cleanup when ref prop changes on re-render in honojs/hono#5264
• fix(reg-exp-router): associate wildcard middleware with matching routes in honojs/hono#5266
• perf(router): share null object creation in honojs/hono#5267

... (truncated)

Commits

• eebdf7b 4.13.7
• 2b8ed40 Merge commit from fork
• cac0c4d 4.13.6
• dac5d57 refactor(on-handler): use forEach for consistent handler iteration (#5326)
• ec648d6 chore: bump editorconfig-checker (#5336)
• e2740d5 fix(types): allow symbol keys in Context<any> get and set fallbacks (#5300)
• 499c35e fix(client): normalize root WebSocket URLs (#5291)
• 50b8788 fix(client): keep a param value of "index" in $url() and $path() (#5297)
• 06880c4 4.13.5
• 531e9c5 Merge commit from fork
• 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.

[roger-guifav]

TL;DR

Atualizacao de uma biblioteca de servidor HTTP (hono), que entra no projeto indiretamente pelo prisma, da versao 4.12.28 para 4.13.7. E uma atualizacao menor, sem mudancas incompativeis anunciadas, e ainda traz correcoes de seguranca. Instalacao, verificacao de tipos e suite de testes passaram na validacao local. Seguro para merge.

Verdict: Approve

(revisado no head SHA fd24e08)

Parecer

Bump minor do hono em /app, aberto pelo bot de dependencias. A hono e dependencia transitiva (entra via node-server e pelo pacote de desenvolvimento do prisma); o manifesto nao muda e o diff toca apenas o lockfile, conferido contra a API. As notas de release da linha 4.13.x nao anunciam breaking changes: o minor inicial e focado em performance e as revisoes seguintes trazem correcoes, incluindo duas de seguranca (escapamento de HTML no renderer jsx e parser de query string). O app nao usa o renderer jsx da hono diretamente, entao a exposicao pratica era baixa, mas o bump reduz risco sem custo. Ha outros tres PRs de bump que tocam o mesmo lockfile; apos o primeiro merge, os demais sao rebaseados pelo proprio bot, sem acao manual. Pergunta de merge: mergearia e dormiria tranquilo — sim.

Criticos (P0)

nenhum

Bloqueadores de correcao (P1)

nenhum

Enderecar no PR (P2)

nenhum

Enderecar no PR (P3 / nits)

nenhum

Acoes que somente o humano pode fazer (ainda...)

nenhuma alem do merge

Verificado

• diff contra a main fresca toca apenas o lockfile do app; contagem de arquivos confere com a API
• npm ci ok; prisma generate ok
• tsc --noEmit: 0 erros; baseline no merge-base tambem 0 erros, ou seja, nenhum erro novo
• vitest: 680 testes passaram, 8 skipped, 0 falhas
• notas de release da hono 4.13.0 a 4.13.7 lidas; nenhum breaking change anunciado

---

Roger (Hermes KVM) - review v2 - fd24e08