release: v0.1.1220

[kojiwakayama]

Cuts framework v0.1.1220 so the environment active-release fix can reach production.

Why now

veryfront-code#3491 landed after v0.1.1219 was cut, so it is in no release. Production runs 0.1.1218, two releases behind the fix.

That fix ends a live outage: every release-bound scheduled run has failed with HTTP 403 since 2026-08-05, because the environment resolver read active_release_id from the top level of the environments response while the API returns it nested under deployment.release.id. 61 failures on agentic-job-submission-processing alone, whose schedule is currently paused because of it. Tracked as veryfront-issue-inbox#417.

Contents

Everything on main since v0.1.1219:

• #3491 read the environment active release from its deployment — the outage fix
• #3492 guard the hosted child completion dispatch
• #3493 keep the real cause when a child error coincides with an abort

How this was prepared, and what was skipped

deno task release --yes --no-publish --no-test --no-build, then the local tag deleted and the commit reworded to the release: vX convention used on main. The branch carries no tag, so nothing publishes until this merges and a tag is created deliberately.

--no-test and --no-build were forced, not chosen. Both gates fail on the same pre-existing defect: scripts/build/build-npm-extension-packages.ts imports #dnt, which 61728ffc9 (#3212) removed from deno.json without removing the script. deno task test sweeps scripts/ and dies on it; verify:dist runs the same build script. Filed as veryfront-issue-inbox#425.

That skip has a trap. --no-build also skips deno task generate, which left hydration-runtime.generated.ts reporting 0.1.1219 while deno.json and version-constant.ts said 0.1.1220. Caught by comparing this commit against v0.1.1219 — two files versus three. deno task generate was run separately and amended in, so all three now agree and the diff matches v0.1.1219s shape.

Worth checking whether an earlier release shipped that skew, since anyone cutting past the broken import would hit it silently.

Verification

The release script could not run its own gates, so the product code was exercised directly: src/server/project-env and src/agent, 1,150 passed, 0 failed. CI on this PR is the real gate.

After merge

Tag v0.1.1220, then promote veryfront-server onto it as fa3ce69 did for v0.1.1218. Only then does the 403 clear and the schedule become re-enableable — which in the same tick should also produce the first run carrying elapsedMs from #3483, never yet observed end to end.

Summary by CodeRabbit

• Chores
  • Updated the package version to 0.1.1220.
  • Updated the displayed application version to match.

[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: b778b76c-fcdf-42ca-b510-b8b5968cb4bf

📥 Commits

Reviewing files that changed from the base of the PR and between e00217a and db97d28.

⛔ 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

---

📝 Walkthrough

Walkthrough

The release version changed from 0.1.1219 to 0.1.1220 in the package configuration and exported version constant.

Changes

Version metadata

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

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

Possibly related PRs

• veryfront/veryfront-code#3486: Updates the same release version fields.
• veryfront/veryfront-code#3488: Updates the same release version metadata.
• veryfront/veryfront-code#3478: Applies the same release-version bump pattern.

Suggested reviewers: kwakayama

🚥 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 version release, which matches the pull request's primary change.
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

📝 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.1220

---

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