release: v0.1.1255

[kwakayama]

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

Why now

veryfront-code#4340 (documents.readonly removal) and #4224 (full drive removal) are both merged but reach no environment while main carries the -rc suffix — version-check publishes suffixed versions as RC only. Both are prerequisites for the Google OAuth verification reply (veryfront/veryfront-issue-inbox#279).

Files

Mirrors the v0.1.1254 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 — confirmed by the staleness check below.

Verified

• 0.1.1255 is above both main (0.1.1255-rc) and npm latest (0.1.1254), so the release job will not no-op
• deno task typecheck — exit 0, no is stale output

Summary by CodeRabbit

• Release
  • Promoted the package from release candidate to stable version 0.1.1255.
  • Updated the displayed version information to consistently show 0.1.1255.

[greptile-apps]

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

[github-actions]

📦 Client bundle boundary

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

[kwakayama]

Code Review — Score: 96/100 (excellent)

Trivial, mechanical release PR — this is essentially config, not logic, so it's scored on correctness/process rather than design or test coverage.

Strengths

• Change is exactly what it claims to be: deno.json, src/utils/version-constant.ts, and the generated hydration-runtime.generated.ts all bump 0.1.1255-rc → 0.1.1255 in lockstep — verified the embedded version string in the generated file directly and it matches.
• templates/manifest.generated.ts was correctly left untouched, and the PR body explains why (staleness check found no diff) rather than silently omitting it — good transparency for a generated-file release PR.
• PR description gives clear rationale (unblocks two merged PRs — documents.readonly/drive scope removal — from reaching npm latest because main is stuck on an -rc suffix) and links the downstream motivation (OAuth verification reply).
• Author states they ran deno task typecheck (exit 0, no "is stale" output) before opening — good practice for a PR that touches a generated file.
• Mirrors the prior v0.1.1254 release pattern per the description, so it's following established repo convention rather than improvising.

Minor notes (non-blocking)

• No independent way to verify "above npm latest" claim from the diff alone — that's an external-state assertion, not really reviewable in-PR; presumably enforced by the version-check/publish CI job.
• CI was still mostly in_progress at review time (coverage shards, tests, lint, typecheck) — worth confirming green before merge, standard for any PR but doubly so for a release cut.

Nothing here warrants a lower score — no code logic changed, diff is minimal and self-consistent, and the description does the legwork of explaining why each file did or didn't change.

---

Generated by Claude Code

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 36537bd7-3560-4828-a9c8-494009a11ba4

📥 Commits

Reviewing files that changed from the base of the PR and between ffce685 and 512d835.

⛔ 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 package version changed from 0.1.1255-rc to 0.1.1255 in deno.json and the exported VERSION constant.

Changes

Stable version release

Layer / File(s)	Summary
Update version identifiers deno.json, src/utils/version-constant.ts	The package metadata and exported VERSION constant now use 0.1.1255 without the release-candidate suffix.

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

Merge Risk: ⚪ Minimal · up to 512d8

This change promotes the package from the release-candidate version to the stable 0.1.1255 release without changing application behavior, authentication, routing, or data access. No actionable merge-blocking risk remains after normal checks and review.

Suggested reviewers: kojiwakayama

🚥 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 release version promoted from the release candidate to the stable v0.1.1255 release.
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.

Full details: Docstring Coverage

Explanation

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 files. (1 skipped: 1 unsupported.)

✨ 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.1255

---

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]

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.1255 removes the -rc suffix so the release job publishes to npm with the latest tag, unblocking prerequisite merges for Google OAuth verification. No issues found.

Options

Display: compact → Showing less information.

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

Compact

gitar display:verbose

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

[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-08-31T10:48:36.996295Z	512d835	Manual request

ℹ️ 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

[kwakayama]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. What shall we delve into next?

Reviewed commit: 512d8350d9

ℹ️ 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".