release: v0.1.1206

[kwakayama]

Bumps the framework to v0.1.1206 so the two render-path fixes now in the merge queue can reach production.

What this release carries

PR	fix
#3409	module pin conflict gated on the cohort, not the flag — every client module of every hosted project answered 409 Unknown dependency snapshot, so no page hydrated
#3411	default CSP admits the platform asset origins the renderer emits — React from the ESM CDN and optimized images were blocked by the policy attached to the same response

Both are green and queued ahead of this PR (positions 3 and 4). This one is deliberately last so a single release ships both.

Why it is a separate PR

The bump belonged in #3411, but that branch is already in the merge queue and GitHub refuses pushes to queued branches:

A pull request for this branch has been added to a merge queue.
Branches that are queued for merging cannot be updated.

Dequeuing a green PR to slip a version line in is more disruptive than a three-line release PR, so this is the smaller move.

Contents

deno.json, src/utils/version-constant.ts, and the generated hydration runtime, which embeds the version string. Three files, +3/-3.

Regenerating the hydration runtime is not optional: it carries the version literal, and a stale copy reds ci (typecheck) rather than failing anywhere obvious. Verified no 0.1.1205 remains in any of the three.

After this merges

Publishing v0.1.1206 is only the first link. Production still needs: framework release → repository_dispatch → veryfront-server rebuild → staging verification → production promotion PR. Until that finishes, hosted pages still do not hydrate.

[chatgpt-codex-connector]

Codex usage limits have been reached for code reviews. Please check with the admins of this repo to increase the limits by adding credits.
Repo admins can enable using credits for code reviews in their settings.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 23 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: 37d39f2e-5c0f-4e10-92c8-9b5fbff0b5b1

📥 Commits

Reviewing files that changed from the base of the PR and between f306473 and 855de00.

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

[kwakayama]

Superseded by #3417, which consolidates this with the other queued render-path fixes plus the v0.1.1206 bump so one queue pass lands the set.

Dequeued from the merge queue to avoid this merging underneath the consolidated branch and leaving it empty or conflicting. Please do not re-queue — merge #3417 instead. Closing once that lands.