Release v0.1.1227

[kojiwakayama]

Version bump only: 0.1.1226 to 0.1.1227.

Three files change by one generated version literal each: deno.json, src/utils/version-constant.ts, and the hydration runtime bundle. The bundle was regenerated with scripts/build/prebundle-hydration-runtime.ts. deno task generate:manifests:check reports every generated artifact current.

Ships

• fix(cross-runtime): make YAML, workspace imports and std/testing resolve off Deno (fix(cross-runtime): make YAML, workspace imports and std/testing resolve off Deno #3526)
• fix(agent): preserve output after trailing model failure (fix(agent): preserve output after trailing model failure #3533, veryfront/veryfront-issue-inbox#338)

Release path

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

At merge time, ensure main has not reached 0.1.1227 through another release PR. If it has, this branch must move to the next unpublished patch version.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 13 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: a544a406-addd-4d93-ab84-009f6d24a5a0

📥 Commits

Reviewing files that changed from the base of the PR and between d110ee2 and 29a661b.

⛔ 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.}

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 29a661b943

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".