Skip to content

chore(release): v0.1.1228 - #3545

Closed
kwakayama wants to merge 1 commit into
mainfrom
release/0.1.1228
Closed

kwakayama wants to merge 1 commit into
mainfrom
release/0.1.1228

Conversation

@kwakayama

@kwakayama kwakayama commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

Cuts v0.1.1228, the release that unblocks veryfront build.

Merging this publishes: version-check (cicd.yml:469) compares deno.json against the previous commit, and a changed stable version gates the release job.

Why this release matters

veryfront build has been broken for every project since 0.1.1206 — 22 releases. An external report surfaced it on 0.1.1227 (veryfront-issue-inbox#456).

There is no earlier version to pin to. 0.1.1205 fails the same templates with the CSSProcessor error that #3417 was fixing. A release is the only fix path.

What ships

PR Fix
#3538 Prime host contracts in the build extension path
#3541 Resolve server-side esm.sh modules with a server target
#3542 Keep optional Deno imports optional
#3540 Isolate cwd-mutating unit tests

Verification on merged main (48cd2d5c7)

All 7 scaffold templates, each veryfront init + veryfront build from scratch:

Template Result Pages
minimal ✓ 4.87s 2
ai-agent (default) ✓ 7.04s 1
docs-agent ✓ 6.83s 2
agentic-workflow ✓ 2.50s 1
multi-agent-system ✓ 3.26s 1
coding-agent ✓ 4.24s 1
saas-starter ✓ 4.72s 3

Before these fixes, 5 of the 7 failed. Page counts are included because veryfront build can exit 0 with zero pages, so "built" alone is not evidence.

Hydration checked in a real browser on the docs-agent build served via veryfront serve: 428 requests all 200, zero console messages, React fibers attached. That matters because #3541 makes SSR evaluate esm.sh's node build while the browser still gets es2022, and a parity break there would be invisible to CI.

Diff

Two lines. deno.json and src/utils/version-constant.ts must move together; src/utils/version.test.ts:25 enforces it.

Summary by CodeRabbit

  • Chores
    • Updated the application version to 0.1.1228.

Ships the build fixes for veryfront-issue-inbox#456. `veryfront build` has
been broken for every project since 0.1.1206, and 5 of 7 scaffold templates
could not build at all.

- #3538 prime host contracts in the build extension path
- #3541 resolve server-side esm.sh modules with a server target
- #3542 keep optional Deno imports optional
- #3540 isolate cwd-mutating unit tests

There is no earlier version to pin to: 0.1.1205 fails the same templates with
the CSSProcessor error that #3417 was fixing.
@kwakayama
kwakayama enabled auto-merge August 10, 2026 17:22
@coderabbitai

coderabbitai Bot commented Aug 10, 2026

Copy link
Copy Markdown

Review Change Stack

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: 587f70de-1a1a-464b-8dbb-93e0d9e85920

📥 Commits

Reviewing files that changed from the base of the PR and between 48cd2d5 and 22e3eea.

📒 Files selected for processing (2)
  • deno.json
  • src/utils/version-constant.ts

📝 Walkthrough

Walkthrough

The release version changed from 0.1.1227 to 0.1.1228 in package metadata and the shared exported version constant.

Changes

Release version update

Layer / File(s) Summary
Synchronize release version
deno.json, src/utils/version-constant.ts
The package version and exported VERSION constant now report 0.1.1228.

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

Possibly related PRs

Suggested reviewers: kojiwakayama, copilot

🚥 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 and matches the primary changes to the project version metadata.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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 💡 1
🛠️ Fix failing CI checks 💡
  • Create stacked PR
  • Commit on current branch
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release/0.1.1228

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

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 22e3eea8b3

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

Comment thread src/utils/version-constant.ts
@kwakayama kwakayama closed this Aug 10, 2026
auto-merge was automatically disabled August 10, 2026 17:46

Pull request was closed

This was referenced Aug 10, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants