release: veryfront 0.1.1260

[kwakayama]

Description

Release veryfront 0.1.1260 from the 0.1.1260-rc prerelease line. On main, CI publishes the stable version (npm latest, JSR, binaries) and dispatches veryfront-code-released to veryfront-server.

The diff matches the previous release (#4501): the deno.json version, src/utils/version-constant.ts, and the version string in the generated hydration bundle (deno task generate, version-only change; generate:manifests:check passes).

Ships 33 commits since 0.1.1259, including:

• fix(provider): bound streamed content by bytes, not delta count #4547: bound streamed provider content by bytes, not delta count. This fixes agent tool calls that stream for longer than ~110 s (veryfront/veryfront-issue-inbox#1627).
• feat(provider): route Veryfront Cloud models by wire surface #4536 / refactor(provider): separate the Veryfront Cloud catalog data tables from the resolution logic #4535: route Veryfront Cloud models by wire surface.
• fix(provider): classify a max_tokens-truncated Anthropic response instead of masking it #4516: classify max_tokens-truncated Anthropic responses.

Verification

• Staging runs 0.1.1260-rc.19878 (the main tip before this bump). A project-agent run on staging (ingestion-agent, single create_file tool call streaming for 426.6 s / 59,175 output tokens) completed without error. Details: veryfront/veryfront-issue-inbox#1622.

Related Issue(s)

Part of veryfront/veryfront-issue-inbox#1622

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update
• Code refactoring
• Performance improvement
• Test update

Checklist

• I have made corresponding changes to the documentation (if applicable)
• I have added tests that prove my fix is effective or that my feature works

Summary by CodeRabbit

• Release
  • Promoted version 0.1.1260 from release candidate status to the final release.
  • Updated the displayed application version to 0.1.1260.

[chatgpt-codex-connector]

You have reached your Codex usage limits for security reviews. Please try again later.

[greptile-apps]

Your trial has ended. Reactivate Greptile to resume code reviews.

[github-actions]

📦 Client bundle boundary

Entrypoint	Modules	Source size	Server leaks
src/index.client.ts	290	2322 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]

Understand this PR’s impact

Explore downstream dependencies and potential security impact with Blast Radius.

View blast radius →

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Advanced

Run ID: 9493976b-faa7-4b54-b3e1-98ac9d15ba8d

📥 Commits

Reviewing files that changed from the base of the PR and between d7bd20d and 08e9d4c.

⛔ 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 project version changes from 0.1.1260-rc to 0.1.1260 in deno.json and the shared VERSION constant.

Changes

Version finalization

Layer / File(s)	Summary
Synchronize version sources deno.json, src/utils/version-constant.ts	The project metadata and exported VERSION constant now use 0.1.1260 instead of 0.1.1260-rc.

Priority: ⬇️ Low

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

Change: Other

🚥 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 this pull request as the release of veryfront version 0.1.1260, which matches the primary changes.
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

• Commit to this branch
• Create a new PR

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

---

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

[gitar-bot]

Important

You are using the Gitar free plan. Upgrade to unlock code review, CI analysis, auto-apply, custom automations, and more.

_Gitar

[kwakayama]

Code Review: 96/100 — Trivial, mechanical version-bump release PR

Summary: This is a release-cut PR with no functional code changes — verified.

Findings:

• ✅ Diff is exactly 3 files / 3 lines: deno.json version field, src/utils/version-constant.ts, and the embedded version string inside the generated hydration bundle (hydration-runtime.generated.ts).
• ✅ I diffed the two (large, minified) bundle strings in hydration-runtime.generated.ts byte-for-byte after normalizing the version substring — confirmed the only difference is 0.1.1260-rc → 0.1.1260. No other content in the generated bundle changed, consistent with the PR description's claim that this is a deno task generate version-only regeneration.
• ✅ Pattern matches the prior release PR (release: veryfront 0.1.1259 #4501) as stated, and the PR description is thorough: it documents the 33 commits since 0.1.1259, links the staging verification (long-running streaming test on 0.1.1260-rc.19878), and links the tracking issue.
• ✅ Commit message is clear and conventional (release: veryfront 0.1.1260), single commit as expected for a release bump.
• ℹ️ Minor nit (non-blocking): the PR checklist boxes for "tests added" and "docs updated" are left unchecked — expected/fine for a release-bump PR, just flagging that the template wasn't tailored (e.g. with a note like "N/A — release PR").

No concerns — this PR is exactly what it claims to be, and I could verify that mechanically rather than just taking the description's word for it. Approving from a code-review standpoint.

---

Generated by Claude Code

[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-21T19:10:20.830939Z	08e9d4c	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.

[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