chore(deps): bump h3 from 2.0.1-rc.25 to 2.0.1-rc.26

[dependabot]

Bumps h3 from 2.0.1-rc.25 to 2.0.1-rc.26.

Release notes

Sourced from h3's releases.

v2.0.1-rc.26

compare changes

🚀 Enhancements

• resolveDotSegments: Add mergeSlashes option (9581407)
• session: Default session cookie to SameSite=Lax (acf8d77)
• ⚠️ Escape interpolated values in html tagged template (#1459)
• readValidatedBody: Support readBody options (#1476)
• Add onDispose hook (#1488)
• defineValidatedHandler: Support async validation (#1491)
• sse: Allow returning EventStream directly from handlers (#1508)

🔥 Performance

• Single-scan fast-path guard for resolveDotSegments (#1458)
• cookie: Avoid quadratic chunked cookie parsing and header rebuilds (#1472)
• middleware: Precompose middleware chains (#1475)
• body-limit: Stream enforcement instead of pre-buffering (#1500)

🩹 Fixes

• resolveDotSegments: Preserve trailing slash on trailing dot segments (ca7de07)
• cookie: Dedup cookies with leading-dot / mixed-case domains (#1462)
• cors: Warn on credentials with null origin (#1464)
• Decode Basic-auth credentials as UTF-8 (#1463)
• proxy: forwardHeaders must not override framing headers (#1467)
• cookie: Cap chunk count in setChunkedCookie (#1469)
• cors: Set single-valued CORS headers instead of appending (#1466)
• auth: Harden basic-auth realm handling and credential timing (#1468)
• validate: Convert malformed JSON to 400 in validated-handler path (#1465)
• base: Collapse leading-slash run in all base-stripping sites (#1471)
• html: Make raw() trust marker unforgeable and hoist escape map (#1473)
• json-rpc: Use -32600 for valid-JSON non-object bodies (#1483)
• Only discard prepared headers for error responses (#1486)
• event-stream: Correct stream teardown on close and client disconnect (#1484)
• deprecated: Correct v1 signatures in the compat shim (#1492)
• response: Do not render non-Error throws as successful responses (#1485)
• event: Keep event.context and req.context as one reference (#1499)
• response: Absorb errors thrown in onResponse hook (4a32c1b)
• response: Route synchronous prepareResponse throws through the error pipeline (#1503)
• response: Keep content-length header for Uint8Array responses (#1504)
• response: Strip HEAD body when merging prepared headers into a mutable Response (#1490)
• response: Allow status and headers staged during the first stream chunk (#1512)

💅 Refactors

• request: ⚠️ Make x-forwarded-proto trust opt-in (#1461)
• event-stream: ⚠️ Drop autoclose option (#1495)
• sse: Promote EventStream to public API, deprecate createEventStream (#1509)

... (truncated)

Changelog

Sourced from h3's changelog.

v2.0.1-rc.26

compare changes

🚀 Enhancements

• resolveDotSegments: Add mergeSlashes option (9581407)
• session: Default session cookie to SameSite=Lax (acf8d77)
• ⚠️ Escape interpolated values in html tagged template (#1459)
• readValidatedBody: Support readBody options (#1476)
• Add onDispose hook (#1488)
• defineValidatedHandler: Support async validation (#1491)
• sse: Allow returning EventStream directly from handlers (#1508)

🔥 Performance

• Single-scan fast-path guard for resolveDotSegments (#1458)
• cookie: Avoid quadratic chunked cookie parsing and header rebuilds (#1472)
• middleware: Precompose middleware chains (#1475)
• body-limit: Stream enforcement instead of pre-buffering (#1500)

🩹 Fixes

• resolveDotSegments: Preserve trailing slash on trailing dot segments (ca7de07)
• cookie: Dedup cookies with leading-dot / mixed-case domains (#1462)
• cors: Warn on credentials with null origin (#1464)
• Decode Basic-auth credentials as UTF-8 (#1463)
• proxy: ForwardHeaders must not override framing headers (#1467)
• cookie: Cap chunk count in setChunkedCookie (#1469)
• cors: Set single-valued CORS headers instead of appending (#1466)
• auth: Harden basic-auth realm handling and credential timing (#1468)
• validate: Convert malformed JSON to 400 in validated-handler path (#1465)
• base: Collapse leading-slash run in all base-stripping sites (#1471)
• html: Make raw() trust marker unforgeable and hoist escape map (#1473)
• json-rpc: Use -32600 for valid-JSON non-object bodies (#1483)
• Only discard prepared headers for error responses (#1486)
• event-stream: Correct stream teardown on close and client disconnect (#1484)
• deprecated: Correct v1 signatures in the compat shim (#1492)
• response: Do not render non-Error throws as successful responses (#1485)
• event: Keep event.context and req.context as one reference (#1499)
• response: Absorb errors thrown in onResponse hook (4a32c1b)
• response: Route synchronous prepareResponse throws through the error pipeline (#1503)
• response: Keep content-length header for Uint8Array responses (#1504)
• response: Strip HEAD body when merging prepared headers into a mutable Response (#1490)
• response: Allow status and headers staged during the first stream chunk (#1512)

💅 Refactors

• request: ⚠️ Make x-forwarded-proto trust opt-in (#1461)
• event-stream: ⚠️ Drop autoclose option (#1495)

... (truncated)

Commits

• 64ebd14 chore(release): v2.0.1-rc.26
• 6e24eb3 chore: update deps
• 6ebd459 fix(response): allow status and headers staged during the first stream chunk ...
• 321b1dc chore: apply automated updates
• 50266f3 chore: update docs
• ba42947 chore: update undocs
• dd19737 refactor(sse): promote EventStream to public API, deprecate createEventStream...
• c82019d feat(sse): allow returning EventStream directly from handlers (#1508)
• 8dc8a28 fix(response): strip HEAD body when merging prepared headers into a mutable R...
• 5cba776 fix(response): keep content-length header for Uint8Array responses (#1504)
• Additional commits viewable in compare view

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
clawhub	Ready	Preview	Aug 18, 2026 8:47pm

[clawsweeper]

Codex review: needs maintainer review before merge. Reviewed August 18, 2026, 4:48 PM ET / 20:48 UTC.

ClawSweeper review

What this changes

Updates ClawHub’s direct production H3 HTTP framework dependency from 2.0.1-rc.25 to 2.0.1-rc.26 and refreshes the Bun lockfile resolutions.

Merge readiness

⚠️ Ready for maintainer review - 2 items remain

The earlier lockfile-integrity blocker is fixed: the current head retains the Carapace SHA-512 entry while updating only h3 and its srvx resolution. The dependency is used by production HTTP and auth routes, so this otherwise-correct update needs after-fix runtime proof before merge.

Priority: P2
Reviewed head: 6c8bfcad2ccd938458089dd0405e9a38d1f6dbe2

Review scores

Measure	Result	What it means
Overall readiness	🦞 diamond lobster (5/6)	PR readiness rating was derived from proof quality, review findings, security review, and reviewer confidence.
Proof confidence	🌊 off-meta tidepool	Not applicable: Real behavior proof is not required for maintainer- or bot-authored pull requests.
Patch quality	🦞 diamond lobster (5/6)	No actionable review findings were identified.

Verification

Check	Result	Evidence
Real behavior	Not applicable	Not applicable: Real behavior proof is not required for maintainer- or bot-authored pull requests.
Evidence reviewed	4 items	Direct production dependency: Current main declares h3 as a direct production dependency, while the PR head changes that declaration to 2.0.1-rc.26. Owned runtime surface: Current main imports H3 for the Convex proxy, which handles request URLs and proxy responses for ClawHub HTTP traffic. Prior integrity finding resolved: The current PR head retains the SHA-512 integrity value for the unchanged @openclaw/carapace Git dependency; the prior ClawSweeper blocker is no longer present.
Findings	None	None.
Security	None	None.

Live Verification

Command: bun test server/convexProxy.test.ts

Result: PASS (completed)

36 |     vi.unstubAllGlobals();
            ^
TypeError: vi.unstubAllGlobals is not a function. (In 'vi.unstubAllGlobals()', 'vi.unstubAllGlobals' is undefined)
      at ‹anonymous› (/tmp/clawsweeper-live-proof-3411-uopDyA/target/server/convexProxy.test.ts:36:8)

::error file=../../../../../tmp/clawsweeper-live-proof-3411-uopDyA/target/server/convexProxy.test.ts,line=36,col=8,title=TypeError: vi.unstubAllGlobals is not a
 function. (In 'vi.unstubAllGlobals()', 'vi.unstubAllGlobals' is undefined)::%0A      at ‹anonymous› (/tmp/clawsweeper-live-proof-3411-uopDyA/target/server/conv
exProxy.test.ts:36:8)
✗ Convex HTTP proxy › rejects an unsigned archive manifest from the paired Convex origin [0.37ms]
31 |
32 | describe("Convex HTTP proxy", () =› {
33 |   afterEach(() =› {
34 |     vi.useRealTimers();
35 |     vi.restoreAllMocks();
36 |     vi.unstubAllGlobals();
            ^
TypeError: vi.unstubAllGlobals is not a function. (In 'vi.unstubAllGlobals()', 'vi.unstubAllGlobals' is undefined)
      at ‹anonymous› (/tmp/clawsweeper-live-proof-3411-uopDyA/target/server/convexProxy.test.ts:36:8)

::error file=../../../../../tmp/clawsweeper-live-proof-3411-uopDyA/target/server/convexProxy.test.ts,line=36,col=8,title=TypeError: vi.unstubAllGlobals is not a
 function. (In 'vi.unstubAllGlobals()', 'vi.unstubAllGlobals' is undefined)::%0A      at ‹anonymous› (/tmp/clawsweeper-live-proof-3411-uopDyA/target/server/conv
exProxy.test.ts:36:8)
✗ Convex HTTP proxy › verifies the paired Convex signature and rejects a modified manifest [46.91ms]
439 |           }),
440 |         );
441 |       }
442 |       throw new Error(ˋUnexpected fetch: ${url}ˋ);
443 |     });
444 |     vi.stubGlobal("fetch", fetchMock);
             ^
TypeError: vi.stubGlobal is not a function. (In 'vi.stubGlobal("fetch", fetchMock)', 'vi.stubGlobal' is undefined)
      at ‹anonymous› (/tmp/clawsweeper-live-proof-3411-uopDyA/target/server/convexProxy.test.ts:444:8)

::error file=../../../../../tmp/clawsweeper-live-proof-3411-uopDyA/target/server/convexProxy.test.ts,line=444,col=8,title=TypeError: vi.stubGlobal is not a func
tion. (In 'vi.stubGlobal("fetch", fetchMock)', 'vi.stubGlobal' is undefined)::%0A      at ‹anonymous› (/tmp/clawsweeper-live-proof-3411-uopDyA/target/server/con
vexProxy.test.ts:444:8)
31 |
32 | describe("Convex HTTP proxy", () =› {
33 |   afterEach(() =› {
34 |     vi.useRealTimers();
35 |     vi.restoreAllMocks();
36 |     vi.unstubAllGlobals();
            ^
TypeError: vi.unstubAllGlobals is not a function. (In 'vi.unstubAllGlobals()', 'vi.unstubAllGlobals' is undefined)
      at ‹anonymous› (/tmp/clawsweeper-live-proof-3411-uopDyA/target/server/convexProxy.test.ts:36:8)

::error file=../../../../../tmp/clawsweeper-live-proof-3411-uopDyA/target/server/convexProxy.test.ts,line=36,col=8,title=TypeError: vi.unstubAllGlobals is not a
 function. (In 'vi.unstubAllGlobals()', 'vi.unstubAllGlobals' is undefined)::%0A      at ‹anonymous› (/tmp/clawsweeper-live-proof-3411-uopDyA/target/server/conv
exProxy.test.ts:36:8)
✗ Convex HTTP proxy › produces identical archive bytes when storage streams use different chunk boundaries [3.76ms]
488 |           { headers: { "content-type": ARCHIVE_MANIFEST_CONTENT_TYPE } },
489 |         );
490 |       }
491 |       throw new Error(ˋSecurity boundary crossed: ${url}ˋ);
492 |     });
493 |     vi.stubGlobal("fetch", fetchMock);
             ^
TypeError: vi.stubGlobal is not a function. (In 'vi.stubGlobal("fetch", fetchMock)', 'vi.stubGlobal' is undefined)
      at ‹anonymous› (/tmp/clawsweeper-live-proof-3411-uopDyA/target/server/convexProxy.test.ts:493:8)

::error file=../../../../../tmp/clawsweeper-live-proof-3411-uopDyA/target/server/convexProxy.test.ts,line=493,col=8,title=TypeError: vi.stubGlobal is not a func
tion. (In 'vi.stubGlobal("fetch", fetchMock)', 'vi.stubGlobal' is undefined)::%0A      at ‹anonymous› (/tmp/clawsweeper-live-proof-3411-uopDyA/target/server/con
vexProxy.test.ts:493:8)
31 |
32 
… output truncated …

Assertions:

• PASS expect_output: Convex HTTP proxy

How this fits together

ClawHub’s server uses H3 to accept HTTP requests for route handlers, the Convex backend proxy, and local development auth checks. Requests enter H3, pass through route-specific checks or proxying, and return browser or API responses.

flowchart LR
  A[Browser and API clients] --> B[H3 HTTP runtime]
  B --> C[Route and proxy handlers]
  C --> D[Convex API and archive service]
  D --> E[HTTP responses]

Loading

Before merge

• Resolve merge risk (P1) - This changes the direct HTTP runtime and its srvx resolution; H3 v2.0.1-rc.26 includes proxy-related behavior changes, so a post-update ClawHub server smoke is needed before merge.
• Complete next step (P2) - No mechanical repair remains; the merge blocker is contributor-supplied real runtime proof for a direct HTTP dependency update.

Agent review details

Security

None.

Review metrics

Metric	Value	Why it matters
Dependency diff	2 files affected; 4 added, 4 removed	The branch is narrowly scoped to one direct production HTTP dependency and its Bun lockfile resolutions.

Merge-risk options

Maintainer options:

1. Add a post-update HTTP smoke proof (recommended)
   Run the updated ClawHub server against a safe local or test backend and attach redacted output showing a route or proxy response after the H3 upgrade.
2. Accept the runtime-update risk
   A maintainer may merge without runtime evidence, accepting the compatibility risk of the direct H3 and srvx upgrade.

Technical review

Best possible solution:

Keep the integrity-protected lockfile entry and merge after a redacted real ClawHub runtime proof shows the updated server starts and serves a safe proxy or route request correctly.

Do we have a high-confidence way to reproduce the issue?

Not applicable — this PR is a dependency update, and no reported bug has a separate reproduction path.

Is this the best way to solve the issue?

Unclear — the lockfile correction resolves the prior review finding, but the best merge path still requires proof that ClawHub’s real H3 server behavior remains sound after the upgrade.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against db95517a87f3.

Labels

Label changes:

• add rating: 🦞 diamond lobster: Overall readiness is 🦞 diamond lobster; proof is 🌊 off-meta tidepool and patch quality is 🦞 diamond lobster.
• add status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: Real behavior proof is not required for maintainer- or bot-authored pull requests.
• remove rating: 🧂 unranked krab: Current PR rating is rating: 🦞 diamond lobster, so this older rating label is no longer current.
• remove status: ⏳ waiting on author: Current PR status label is status: 👀 ready for maintainer look.

Label justifications:

• P2: This is a bounded production HTTP-runtime maintenance update without evidence of an active user-facing regression.
• merge-risk: 🚨 security-boundary: H3 is directly imported by ClawHub’s HTTP proxy and local auth route, so its runtime behavior sits on request-security boundaries.
• rating: 🦞 diamond lobster: Overall readiness is 🦞 diamond lobster; proof is 🌊 off-meta tidepool and patch quality is 🦞 diamond lobster.
• status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: Real behavior proof is not required for maintainer- or bot-authored pull requests.

Evidence

What I checked:

• Direct production dependency: Current main declares h3 as a direct production dependency, while the PR head changes that declaration to 2.0.1-rc.26. (package.json:130, 6c8bfcad2ccd)
• Owned runtime surface: Current main imports H3 for the Convex proxy, which handles request URLs and proxy responses for ClawHub HTTP traffic. (server/convexProxy.ts:2, db95517a87f3)
• Prior integrity finding resolved: The current PR head retains the SHA-512 integrity value for the unchanged @openclaw/carapace Git dependency; the prior ClawSweeper blocker is no longer present. (bun.lock:453, 6c8bfcad2ccd)
• Lockfile scope: The supplied PR patch changes two files and updates h3 plus its srvx resolution with lockfile integrity hashes; it does not change application route code. (bun.lock:1339, 6c8bfcad2ccd)

Likely related people:

• dependabot[bot]: The available checkout history is disconnected, but the current proposed h3 and lockfile update is authored by this automation; no human feature-history owner could be reliably attributed locally. (role: dependency update automation; confidence: low; commits: 6c8bfcad2ccd; files: package.json, bun.lock)

Rating scale

Score	Internal tier	Crab rank	Meaning
6/6	S	🦀 challenger crab	Exceptional readiness
5/6	A	🦞 diamond lobster	Very strong readiness
4/6	B	🐚 platinum hermit	Good normal PR; ordinary maintainer review
3/6	C	🦐 gold shrimp	Useful, but confidence is limited
2/6	D	🦪 silver shellfish	Proof or implementation needs work
1/6	F	🧂 unranked krab	Not merge-ready
N/A	NA	🌊 off-meta tidepool	Rating does not apply

Overall follows the weaker of proof and patch quality.
Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

Workflow

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

History

Review history (3 earlier review cycles)

• reviewed 2026-08-05T16:10:02.524Z sha 01936c0 :: needs changes before merge. :: [P1] Restore the Carapace integrity hash
• reviewed 2026-08-11T18:04:15.236Z sha 140794c :: needs changes before merge. :: [P1] Restore the Carapace integrity hash
• reviewed 2026-08-12T19:26:27.583Z sha a902aa8 :: needs changes before merge. :: [P1] Restore the Carapace integrity hash

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	h3@​2.0.1-rc.25 ⏵ 2.0.1-rc.26	+1		+1

View full report

[blacksmith-sh]

Found 2 test failures on Blacksmith runners:

Failures

Test	View Logs
[chromium] › e2e/local-auth/ malicious-skill-ban-flow.pw.test.ts:102:1 › malicious prepublication retries keep the c lean latest visible	View Logs
e2e/local-auth/malicious-skill-ban-flow.pw.test.ts/ malicious prepublication retries keep the clean latest visible	View Logs

^{Need help on this PR? Tag @codesmith-bot with what you need.}