release: 20.1.1 — publish the x verify gate-reporting fix - #436
Merged
Merged
Conversation
The lockstep patch bump that publishes the x verify gate-reporting fix. f515aee (#435, closing #434) made a gate step whose suite executed nothing report as skipped rather than passed, and npm still serves 20.1.0 for all 31 packages, so every bunx create-ultimate scaffold still ships a gate that prints a green check over an e2e lane that never ran. Patch rather than minor: no published API gained or lost a member and no new capability shipped, and the only [Unreleased] section was ### Fixed. Produced by scripts/release.ts --bump patch; no manifest was hand-edited. Derived files moved with the manifests: framework.manifest.json, bun.lock (235 recorded facts), docker/helm/Chart.yaml and the wiki footer's stamp. scripts/release.ts --check 20.1.1 reports 31 packages stamped at 20.1.1 and every file derived from them. bun install and bun install --frozen-lockfile both report no changes. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yml Review profile: ASSERTIVE Plan: Essentials Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (46)
Included review availability: 4 reviews are currently available. Your included PR review attempts over the past 7 days set your current allowance at 5 reviews per hour. 📝 WalkthroughWalkthroughThe release metadata, package manifests, Helm chart, examples, and documentation are updated from 20.1.0 to 20.1.1. The changelog records the CLI behavior fix for suites that execute no tests. ChangesRelease alignment
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~5 minutes Change: Other Suggested reviewers: Merge Risk: ⚪ Minimal · up to This is a metadata-only lockstep release with aligned versions and no source changes, so it is ready to merge. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
The lockstep patch bump to 20.1.1, stamping all 31 publishable packages plus the private
example trees, and promoting
## [Unreleased]to## 20.1.1 - 2026-09-12.Why
f515aee4(#435, closing #434) merged the fix forx verifyreporting a green check over a gatestep whose only test skipped itself, and it is not on npm. This repository publishes only when a
GitHub Release is published (
release.yml:on: release: types: [published]), so the registrystill serves 20.1.0 and every
bunx create-ultimatescaffold still ships the silently-skippinge2egate. Measured before opening this:No bootstrap is owed, so the abort-mid-publish hazard
release.ymlwarns about does not apply tothis run.
Changes
Patch, not minor. #435 is a bug fix to CLI gate reporting: no published API gained or lost a
member, no new capability, and the only
[Unreleased]section was### Fixed.SECURITY.mdstates the same rule from the other direction — a fix ships as a patch to every package in one
release.
47 files, all modified, none added or deleted. Produced entirely by
bun run scripts/release.ts --bump patch— no manifest was hand-edited:examples/dummyanddummy/social-media-clonetrees, which resolve@ultimat3/*out of the same lockfile.CHANGELOG.md:[Unreleased]promoted to20.1.1 - 2026-09-12with### Commitsappendedinside it, and a fresh empty
[Unreleased]opened above.framework.manifest.json(packagesdiffers),bun.lock(235 recorded facts corrected),docker/helm/Chart.yaml, andwiki/_Footer.md(1 stamp).
Verification
Branch cut from
mainatf515aee4. Dry run first, then the write:The question the release workflow asks before it publishes:
bun installand thenbun install --frozen-lockfileboth reported no changes, confirming thebump had already corrected the lock.
The repo gate, run on this branch:
Every one of the 9 failures is this box, not this tree, and that is measured rather than
asserted. The diff contains no source file at all —
git diff --name-onlyis 42package.jsonfiles plusCHANGELOG.md,bun.lock,docker/helm/Chart.yaml,framework.manifest.jsonandwiki/_Footer.md, andgrep -cE '\.(ts|tsx|js|jsx)$'over itanswers
0. A test regression from a version-field rewrite is not possible by construction.The failures, enumerated:
create-ultimatecasesX_BUN_VERSION— the box runs Bun 1.3.14,REQUIRED_BUNis1.4.0. AssertedX_CLI_BAD_FLAG, receivedX_BUN_VERSION, raised before the command does anythingx dev --role(dev-roles.test.ts)beforeEach/afterEachhook timed out at 5serrors.explain(error-fixes.test.ts)x dev … SIGINT(cmd-dev.live.test.ts)The last three are the "port-bind and spawn-hook timeouts" #433 recorded as this box's variance.
Checked directly rather than assumed:
bun test packages/cli/src/error-fixes.test.ts packages/cli/src/dev-roles.test.tson unmodifiedmainatf515aee4gives the identicaltwo
dev-roleshook timeouts at the identical 5s, anderror-fixespasses on both branches whenthe box is not running 8 parallel workers.
None of this reaches the publish decision:
release.ymlrunsbun run scripts/verify.tson apinned
bun-version: 1.4.0before the firstnpm publish, so a tree that is actually brokencannot reach the registry.
One thing CI does not cover
This build box runs Bun 1.3.14 against
REQUIRED_BUN=1.4.0(
packages/cli/src/app-root.ts, andengines.bun).release.ymlpinsbun-version: 1.4.0, sothe gate that actually gates the publish runs above the floor; the local red is the box, not the
tree. PR #433 recorded the same gap.
A stale claim in PUBLISHING.md, not fixed here
PUBLISHING.md§ 2 still reads "No required reviewers, by the owner's decision on 2026-09-05",and § "Ongoing releases" step 4 reads "Nobody approves anything". Both are now false: #432 is
closed and the
npm-publishenvironment carriesrequired_reviewers(sebyx07, ivndev001) besideits
v*tag policy, which is whatrelease.yml's own header comment has always said it should.The publish for this tag will pause for approval. Left out of this PR deliberately — a release
stamp is script-produced and should stay that way — and worth its own change.
🤖 Generated with Claude Code
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.Summary by CodeRabbit
Bug Fixes
Release
Documentation