chore: open the 0.1.1260-rc prerelease line so main publishes again - #4518
Conversation
veryfront-code publishes only when version-check reports is_stable=false. deno.json held the released 0.1.1259, a plain semver, so every merge since has logged "Stable version unchanged -> skipping publication" and published nothing -- including #4514, the undated model-id output-cap fix. Moving the base to 0.1.1260-rc makes CI publish 0.1.1260-rc.<run> per main build again, matching the RC line veryfront-agent already consumes (0.1.1259-rc.19435). Regenerated hydration-runtime.generated.ts, which embeds the version.
|
You have reached your Codex usage limits for security reviews. Please try again later. |
There was a problem hiding this comment.
Your trial has ended. Reactivate Greptile to resume code reviews.
📦 Client bundle boundary
A server module in a client graph aborts hydration in the browser. New leaks fail CI; known leaks are tracked in |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Advanced Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (2)
Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review. 📝 WalkthroughWalkthroughThe package version and exported ChangesRelease version alignment
Priority: ➖ Normal Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Bug fix Merge Risk: ⚪ Minimal · up to The release metadata is consistent and CI will route the prerelease through the intended RC publication path. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches 💡 1🛠️ Fix failing CI checks 💡
📝 Generate docstrings
🧪 Generate unit tests (beta)
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. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
@codex review |
|
Codex Review: Didn't find any major issues. More of your lovely PRs please. Reviewed commit: ℹ️ About Codex in GitHubCodex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback". |
|



Why
veryfront-codepublishes an npm build only whenversion-checkreportsis_stable=false(cicd.yml, theprereleasejob).deno.jsonhas held the released0.1.1259— a plain semver — since veryfront-code#4501, sois_stable=trueand every merge to main since has logged:and published nothing. That includes veryfront-code#4514, the fix for veryfront/veryfront-issue-inbox#1480, which is on main (
53b775c0a4) but exists in no consumable build.That matters for the 18 Sep customer demo:
veryfront-agentpinsveryfront: "0.1.1259-rc.19435", an RC of the previous version, so the agent runtime still resolves an undatedanthropic/claude-haiku-4-5to the 4096-token fallback and still producesProvider replay turn failed before its boundary.What this does
Moves the base to
0.1.1260-rc, so CI publishes0.1.1260-rc.<run>per main build again — the same RC lineveryfront-agentalready consumes.deno.json→0.1.1260-rcsrc/utils/version-constant.ts→ kept in sync, asscripts/release.tsdoessrc/html/hydration-script-builder/hydration-runtime.generated.tsregenerated viadeno task generate(it embeds the version)lint,lint:test-typecheckanddocs:api-reference:checkpass.Why not
deno task releaseThe release script commits, tags
v<version>and pushes straight tomain— it bypasses review, and a tag is wrong for opening a prerelease line rather than cutting a stable one.Still required after this merges
veryfrontinveryfront-agent/package.jsonto the0.1.1260-rc.<run>this publishesNeither is automatic, and the demo runs on veryfront.com.
Refs veryfront/veryfront-issue-inbox#1480
Summary by CodeRabbit
0.1.1260-rc.