Release v0.1.1226

[kwakayama]

Version bump only: 0.1.1225 → 0.1.1226.

Three files, one line each — deno.json, src/utils/version-constant.ts, and the hydration runtime bundle that embeds the version. The bundle was regenerated with scripts/build/prebundle-hydration-runtime.ts, not hand-edited; deno task generate:manifests:check reports every other generated artifact current.

Ships

• fix(deploy): stop failing deploys on a probe an API key cannot pass (fix(deploy): stop failing deploys on a probe an API key cannot pass #3527)
• fix(config): keep hosted config filenames exact (fix(config): keep hosted config filenames exact #3531)
• fix(runtime): keep dispatch alive when model context is not cloneable (fix(runtime): keep dispatch alive when model context is not cloneable #3528)
• fix(proxy): keep config workers out of binary graph (fix(proxy): keep config workers out of binary graph #3529)
• fix(platform): remove an empty directory the way Deno does on Node and Bun (fix(platform): remove an empty directory the way Deno does on Node and Bun #3510)
• fix(cli): restore update notifications (fix(cli): restore update notifications #3524)
• test: remove wall-clock races from pre-push suites (test: remove wall-clock races from pre-push suites #3530)
• build: define the verify:dist task the release script already calls (build: define the verify:dist task the release script already calls #3523)
• build(deps): bump the codeql-action group with 2 updates (build(deps): bump the codeql-action group with 2 updates #3525)

Release path

main and npm are both on 0.1.1225, so this bump is above both. On merge, the push to main makes scripts/ci/stable-release-requested.sh see a changed version, and the release job publishes --tag latest, cuts the v0.1.1226 tag, and uploads binaries. No manual tag or dispatch.

Worth re-checking at merge time: if main reaches 0.1.1226 by another route first, this branch's bump becomes a no-op diff and the release silently skips.

[coderabbitai]

Warning

Review limit reached

@kwakayama, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 9 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 90475878-1a13-4c39-90d6-6a7f038ce309

📥 Commits

Reviewing files that changed from the base of the PR and between d68fe07 and 6b421b2.

⛔ Files ignored due to path filters (1)

• src/html/hydration-script-builder/hydration-runtime.generated.ts is excluded by !**/*.generated.*

📒 Files selected for processing (2)

• deno.json
• src/utils/version-constant.ts

---

_{Comment @coderabbitai help to get the list of available commands.}