release: v0.1.1256

[kwakayama]

Promotes main from 0.1.1256-rc to a clean 0.1.1256 so the release job publishes to npm --tag latest.

Why now

latest has been at 0.1.1255 since 2026-08-31 -- 5 days, longer than this repo's typical 1-4 day stable-release cadence. The rc channel has moved on to 0.1.1256-rc.18533, which now carries the full fix chain from this week's staging-401 incident work: veryfront-code#4407 (header-parsing 401 fix), #4411 (DetachedRunTracker crash-loop fix), #4412/#4413 (internal-URL trust hardening for run-scoped inference credentials), all verified end-to-end via a green Remote E2E Health target=staging run (39/39 ai-live, every catalogue model). Anyone consuming veryfront@latest unpinned is still 9 RC builds behind that.

Files

Mirrors the v0.1.1255 release: deno.json, src/utils/version-constant.ts, and the regenerated src/html/hydration-script-builder/hydration-runtime.generated.ts (it embeds the version string). templates/manifest.generated.ts needed no change this time.

Verified

• 0.1.1256 is above both main (0.1.1256-rc) and npm latest (0.1.1255), so the release job will not no-op.
• deno task typecheck -- exit 0, no is stale output.
• This is the exact commit (b894ff492, fix(provider): trust internal cluster hostnames for run-scoped inference credentials #4413's merge) already verified via Remote E2E Health target=staging run 33918528975.

Note

Companion to veryfront-infrastructure#329, which adds veryfront-code's release process to the production-release runbook (previously undocumented there).

Release doc: veryfront-infrastructure#330 (consolidated view of this and four other release PRs prepared the same session). Follow-up: #4415 (draft, stacked, resumes the RC line after this merges).

Summary by CodeRabbit

• Release
  • Updated the application version from release candidate 0.1.1256-rc to stable release 0.1.1256.

[greptile-apps]

kwakayama has reached the 50-credit limit for trial accounts. To continue receiving code reviews, upgrade your plan.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-04T22:22:17.304144Z	ffe89cf	PR opened

ℹ️ 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" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[github-actions]

📦 Client bundle boundary

Entrypoint	Modules	Source size	Server leaks
src/index.client.ts	288	2285 KiB	✅ 0

A server module in a client graph aborts hydration in the browser. New leaks fail CI; known leaks are tracked in scripts/lint/client-bundle-baseline.json to burn down.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Team

Run ID: 555bce65-c0ea-4922-93f2-c0f0d6b6e112

📥 Commits

Reviewing files that changed from the base of the PR and between b0244d4 and ffe89cf.

⛔ 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

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The release version changes from 0.1.1256-rc to 0.1.1256 in deno.json and the exported VERSION constant.

Changes

Stable release version

Layer / File(s)	Summary
Synchronize stable version values deno.json, src/utils/version-constant.ts	The configured version and exported VERSION constant change from 0.1.1256-rc to 0.1.1256.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to ffe89

This updates the release-candidate version to the stable 0.1.1256 value for publishing and version metadata. No current merge-blocking risk remains.

Suggested reviewers: mattboon

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly identifies the stable v0.1.1256 release, which matches the primary change from the release candidate version.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 1…
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/v0.1.1256

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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

[kwakayama]

Review: 94/100 — clean, well-documented mechanical release bump

This is a standard release-promotion PR (0.1.1256-rc → 0.1.1256), not a feature/fix change, and it's about as low-risk as this category gets.

Strengths

• Change is minimal and mechanical: version string updated consistently in deno.json and src/utils/version-constant.ts (both files agree, no drift between the two sources of truth), plus the regenerated hydration-runtime.generated.ts that embeds the version — exactly the three files this repo's release convention touches (mirrors the v0.1.1255 pattern called out in the description).
• PR description is unusually thorough for a version bump: explains why now (5-day-stale latest, cadence norm is 1-4 days), enumerates the fix chain riding along (fix(agent): bind inference token on default chat dispatch #4407, fix(agent): stop a failed detached run from crashing the process #4411, fix(agent): route inference through public API #4412/fix(provider): trust internal cluster hostnames for run-scoped inference credentials #4413), and links a green Remote E2E Health staging run covering the exact commit being promoted.
• Verification section is concrete and checkable: confirms 0.1.1256 sorts above both main and current npm latest (so the release job won't no-op), and states deno task typecheck passed with no staleness warning.
• Correctly calls out that templates/manifest.generated.ts needed no regeneration this time, showing the generated-file set was actually checked rather than blindly copied from the last release.
• Cross-links the companion infra PR (runbook update) for anyone auditing the release process end-to-end.

Concerns (minor, non-blocking)

• mergeable_state is currently blocked and most CI checks were still in_progress at review time — nothing failing, just needs the required checks/approval to land before merge; worth confirming green before merging given this promotes to npm latest.
• The diff for hydration-runtime.generated.ts is a single very large line (whole minified bundle), so it's not practically human-diffable in review — worth double-checking in CI that the generated-file check (version-check job) actually re-derives and byte-compares it rather than trusting it was regenerated correctly by hand/script.

No actionable code changes requested — approve pending green CI.

---

Generated by Claude Code

[Copilot]

🟢 Approval recommended

The change is a consistent, fully-aligned version promotion across the canonical version sources and the generated hydration bundle.

Pull request overview

Promotes the repository version from the 0.1.1256-rc prerelease stream to the stable 0.1.1256 release so the publishing pipeline can ship veryfront@latest to npm. This fits the codebase’s release process by updating the authoritative version in deno.json, the shared runtime constant, and the pre-bundled hydration runtime that embeds the version string.

Changes:

• Bump deno.json package version to 0.1.1256.
• Update src/utils/version-constant.ts to the stable 0.1.1256.
• Regenerate the hydration runtime bundle so it embeds VERSION = "0.1.1256".

Verification noted in PR description:

• deno task typecheck (exit 0, no “is stale” output). Not re-run in this review session.

File summaries

File	Description
deno.json	Sets the published package version to 0.1.1256.
src/utils/version-constant.ts	Keeps the shared VERSION constant in sync with deno.json.
src/html/hydration-script-builder/hydration-runtime.generated.ts	Regenerates the bundled hydration runtime to embed the stable version string.

Review details

• Files reviewed: 2/3 changed files
• Comments generated: 0
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[gitar-bot]

Note

Automatic reviews are paused because your trial's included automatic processing has been used for this period. Upgrade now, or comment "Gitar review" to run a review anytime.
Learn more

Code Review ✅ Approved

Version bump to v0.1.1256 for npm latest release, mirroring the v0.1.1255 release structure with updates to deno.json, version constant, and generated hydration runtime. Changes verified against staging E2E tests and confirmed to be the exact commit already validated through Remote E2E Health. No issues found.

Options

Display: compact → Showing less information.

Comment with these commands to change the behavior for this request:

Compact

gitar display:verbose

---

Important

Your trial ends in 4 days — upgrade now to keep code review, CI analysis, auto-apply, custom automations, and more.

_{Was this helpful? React with 👍 / 👎 | Gitar}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[kwakayama]

Follow-up prepared: #4415 (release: prepare v0.1.1257 RC) bumps main to the next RC line once this merges. Left as draft, stacked on this branch — do not merge #4415 before this one.