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 12, 2026 7:25pm

[clawsweeper]

Codex review: needs changes before merge. Reviewed August 12, 2026, 3:26 PM ET / 19:26 UTC.

ClawSweeper review

What this changes

The PR updates the production h3 dependency from 2.0.1-rc.25 to 2.0.1-rc.26 and refreshes Bun lockfile resolutions.

Merge readiness

⛔ Blocked by patch quality or review findings - 6 items remain

Keep open: the h3 update is useful, but the refreshed lockfile still removes integrity metadata from the unrelated Git-hosted Carapace dependency. The prior P1 blocker remains unresolved.

Priority: P2
Reviewed head: a902aa858fb45cfb9e7fd917397417a3b55e3578

Review scores

Measure	Result	What it means
Overall readiness	🧂 unranked krab (1/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	🧂 unranked krab (1/6)	Security review found an item that needs attention.

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	5 items	Current PR defect: The PR changes h3 but also removes the existing SHA-512 field from the unchanged @openclaw/carapace Git lock entry. Frozen installs rely on this lockfile: The shared Bun setup action installs workspace dependencies with --frozen-lockfile. Affected dependency is production code: Carapace is declared as a production Git dependency and its styles are imported by the application.
Findings	1 actionable finding	[P1] Restore the Carapace integrity hash
Security	Needs attention	Unrelated Git dependency loses integrity metadata: Removing the existing SHA-512 field makes the lock resolution less verifiable without a stated Carapace upgrade or validated lockfile migration.

How this fits together

ClawHub’s server routes use h3, while package.json and Bun’s lockfile define the exact production dependency graph used by builds and CI. The lockfile also records the Git-hosted Carapace UI dependency consumed by the app stylesheet.

flowchart LR
  A[Production manifest] --> B[Bun lockfile]
  B --> C[Frozen dependency install]
  C --> D[Server routes and web build]
  E[Carapace Git integrity hash] --> B

Loading

Before merge

• Restore the Carapace integrity hash (P1) - The h3 refresh also removes the SHA-512 value for the unchanged @openclaw/carapace Git dependency. This weakens verification for frozen Bun installs; retain the existing hash or provide a documented, validated lockfile-format migration.
• Resolve security concern: Unrelated Git dependency loses integrity metadata - Removing the existing SHA-512 field makes the lock resolution less verifiable without a stated Carapace upgrade or validated lockfile migration.
• Resolve merge risk (P1) - Merging removes the integrity value for an unrelated Git-hosted production dependency, reducing supply-chain verification in frozen Bun installs.
• Complete next step (P2) - A repair worker can mechanically restore the dropped integrity field, while contributor-provided real-install proof remains required before merge.
• Improve patch quality - Resolve the security review concern or explain why the changed path is safe.
• Improve patch quality - Address the highest-priority review finding and re-run the changed-surface validation.

Findings

• [P1] Restore the Carapace integrity hash — bun.lock:453
• [medium] Unrelated Git dependency loses integrity metadata — bun.lock:453

Agent review details

Security

Needs attention: The lockfile drops integrity metadata for an unrelated Git-hosted production dependency.

Review metrics

Metric	Value	Why it matters
Dependency diff	2 files affected; +5/-5	The nominal h3 patch update changes an unrelated Git dependency lock entry.

Merge-risk options

Maintainer options:

1. Restore the integrity field before merge (recommended)
   Keep the h3 and srvx updates while restoring the unchanged Carapace SHA-512 lockfile value, then validate frozen dependency resolution.

Copy recommended automerge instruction

@clawsweeper automerge

Special instructions:
Restore the @openclaw/carapace SHA-512 lockfile integrity field while retaining the h3 and srvx resolution update, then validate a frozen Bun install.

Technical review

Best possible solution:

Land the h3 and srvx resolution update only after retaining the existing Carapace SHA-512 field and capturing a redacted successful frozen-install check.

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

Yes: a direct comparison of the PR head and current main deterministically shows the unrelated Carapace integrity value is removed.

Is this the best way to solve the issue?

No: updating h3 is appropriately narrow, but the accompanying loss of Carapace integrity metadata is not required for that update.

Full review comments:

• [P1] Restore the Carapace integrity hash — bun.lock:453
  The h3 refresh also removes the SHA-512 value for the unchanged @openclaw/carapace Git dependency. This weakens verification for frozen Bun installs; retain the existing hash or provide a documented, validated lockfile-format migration.
  Confidence: 0.99

Overall correctness: patch is incorrect
Overall confidence: 0.99

AGENTS.md: found and applied where relevant.

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

Labels

Label justifications:

• P2: This is a bounded production dependency update with a concrete but contained merge blocker.
• merge-risk: 🚨 security-boundary: The diff removes integrity metadata for an unrelated Git-hosted production dependency.
• rating: 🧂 unranked krab: Overall readiness is 🧂 unranked krab; proof is 🌊 off-meta tidepool and patch quality is 🧂 unranked krab.
• status: ⏳ waiting on author: ClawSweeper has contributor-facing work open and is waiting for author action. Not applicable: Real behavior proof is not required for maintainer- or bot-authored pull requests.

Evidence

Security concerns:

• [medium] Unrelated Git dependency loses integrity metadata — bun.lock:453
  Removing the existing SHA-512 field makes the lock resolution less verifiable without a stated Carapace upgrade or validated lockfile migration.
  Confidence: 0.99

Acceptance criteria:

• [P1] bun install --frozen-lockfile.
• [P1] bun run ci:static.
• [P1] bun run ci:types-build.

What I checked:

• Current PR defect: The PR changes h3 but also removes the existing SHA-512 field from the unchanged @openclaw/carapace Git lock entry. (bun.lock:453, a902aa858fb4)
• Frozen installs rely on this lockfile: The shared Bun setup action installs workspace dependencies with --frozen-lockfile. (.github/actions/setup-bun/action.yml:15, 60b02c09f936)
• Affected dependency is production code: Carapace is declared as a production Git dependency and its styles are imported by the application. (package.json:104, 60b02c09f936)
• h3 is a direct runtime dependency: Current server proxy code imports h3 runtime APIs, establishing that this dependency update affects the production server surface. (server/convexProxy.ts:2, 60b02c09f936)
• Area provenance: Recent lockfile history includes Patrick Erichsen’s Carapace upgrade commit, which is the likely origin of the current Carapace lock resolution. (bun.lock:453, 2c7c40f001be)

Likely related people:

• Patrick Erichsen: Authored the recent Carapace v0.6.1 upgrade in the lockfile’s recent history and most recently maintained adjacent dependency work. (role: introduced current Carapace resolution; confidence: high; commits: 2c7c40f001be, 60b02c09f936; files: package.json, bun.lock, src/design-system.css)
• Yiğit ERDOĞAN: Authored the latest Bun dependency-audit update immediately adjacent to this lockfile maintenance surface. (role: recent dependency contributor; confidence: medium; commits: 8b31a7e6e1a5; files: bun.lock, package.json)

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 (2 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