|
| 1 | +# 260901 — v2.39.0 release train: audit, promote, publish |
| 2 | + |
| 3 | +Snapshot taken 2026-09-01T01:35Z. This unit carries `dev` to `preview` and `main` and |
| 4 | +publishes 2.39.0 to npm. It is a delivery unit, not a bug-fix unit: no product code is |
| 5 | +written here unless the regression audit produces a blocker. |
| 6 | + |
| 7 | +## Measured state |
| 8 | + |
| 9 | +| Ref | SHA | `package.json` | |
| 10 | +|-----|-----|-----------------| |
| 11 | +| `origin/dev` | `9af3a7bebb5eb6e9bb9aab51274586897eaaba03` | `2.39.0` | |
| 12 | +| `origin/main` | `ebb4d552e` | `2.38.0` | |
| 13 | +| `origin/preview` | `93704b4f8` | `2.38.0-preview.20260831` | |
| 14 | + |
| 15 | +Promotion delta `origin/main...origin/dev`: 43 commits, 252 files, +18668/-513. |
| 16 | +Neither `main` nor `preview` is an ancestor of `dev` — both carry their own release |
| 17 | +commits, which is the normal shape here. Every promotion in this repository is a merge |
| 18 | +of `dev` into a promotion branch, then a PR into the target. |
| 19 | + |
| 20 | +### Gate evidence at the `dev` head |
| 21 | + |
| 22 | +Cross-platform CI run `33457563882` on `9af3a7beb`: **success**. Every job passed — |
| 23 | +four test shards, `macos`, `gates`, `storage policy`, `api usage`, keyring on all three |
| 24 | +OSes, `npm-global` on all three OSes. The Windows shard matrix is `skipped`, which is its |
| 25 | +normal push-event state; `platform-windows` is `workflow_dispatch`-only. |
| 26 | + |
| 27 | +No Service lifecycle run exists for `9af3a7beb` — that workflow's push trigger is |
| 28 | +path-filtered and the head commit touched none of its paths. |
| 29 | + |
| 30 | +## The preview channel is two cycles stale, and that is not an accident |
| 31 | + |
| 32 | +npm currently advertises `latest=2.38.0` and `preview=2.36.0-preview.20260830`. |
| 33 | + |
| 34 | +The cause is recorded in CI, not in npm. `origin/preview` tip `93704b4f8` carries |
| 35 | +`2.38.0-preview.20260831`, but its push-event Cross-platform CI run `33386559501` |
| 36 | +**failed**: jobs `macos` and `test 1/4` failed while every other job passed. |
| 37 | +`release.yml` requires a *successful* `push`-event `ci.yml` run for the exact SHA on |
| 38 | +the release branch, and deliberately refuses a green pull-request run for the same SHA. |
| 39 | +So the v2.38.0 preview publish was never dispatchable. The stable publish was unaffected |
| 40 | +because `main`'s own promotion run `33385192526` passed. |
| 41 | + |
| 42 | +PR #3073's description already documents an intermittent macOS failure in |
| 43 | +`tests/shutdown-launcher.test.ts` that does not reproduce on Linux. Lane E confirms |
| 44 | +whether run `33386559501` is that same flake or a real defect before we treat the |
| 45 | +preview promotion as routine. |
| 46 | + |
| 47 | +## What the release workflow actually demands |
| 48 | + |
| 49 | +From `.github/workflows/release.yml`, a dispatch must satisfy all of: |
| 50 | + |
| 51 | +1. `expected-sha` — required, full 40 characters, and it must still be the branch tip. |
| 52 | + The guard checks out `.github/scripts/release-dispatch-guard.cjs` from the default |
| 53 | + branch, so the validation code is `main`'s, not the dispatched ref's. |
| 54 | +2. Branch/version/dist-tag coupling. From `main`: stable semver only, dist-tag `latest`. |
| 55 | + From `preview`: the version must contain `-preview.`, dist-tag `preview`. Any other |
| 56 | + ref is refused outright. |
| 57 | +3. A successful `ci.yml` run for the exact SHA, on that branch, from a `push` event. |
| 58 | +4. The service gate, when armed. It diffs the previous *merged* release tag against |
| 59 | + `HEAD` and, if any of `src/service.ts`, `src/cli.ts`, `src/cli/index.ts`, |
| 60 | + `src/lib/bun-runtime.ts`, `package.json`, `bun.lock`, |
| 61 | + `.github/workflows/service-lifecycle.yml` changed, demands a successful |
| 62 | + Service lifecycle run for the same SHA. |
| 63 | + |
| 64 | +**The service gate will be armed for this release.** Measured against the delta: |
| 65 | +`package.json`, `src/cli/index.ts` and `src/service.ts` are all present. Both promotion |
| 66 | +commits therefore need a green Service lifecycle run of their own, and the push trigger |
| 67 | +will supply it because those same paths are in the merge. |
| 68 | + |
| 69 | +Publication is tokenless via Trusted Publishing (OIDC); there is no `NPM_TOKEN` to check. |
| 70 | + |
| 71 | +## Work phases |
| 72 | + |
| 73 | +One phase, one full PABCD cycle. |
| 74 | + |
| 75 | +- **wp0** — this roadmap. Docs only. |
| 76 | +- **wp1** — regression audit of the promotion delta, five parallel `gpt-5.6-sol`/high |
| 77 | + lanes, plus a gate determination. → `010` |
| 78 | +- **wp2** — promote `dev` onto `preview`, publish nothing yet. → `020` |
| 79 | +- **wp3** — promote `dev` onto `main`. → `030` |
| 80 | +- **wp4** — dispatch `release.yml` twice and prove the publish. → `040` |
| 81 | + |
| 82 | +## Success criteria |
| 83 | + |
| 84 | +- c-1 — every audit lane returns a verdict with file/line citations, and no blocker survives. |
| 85 | +- c-2 — the gates `release.yml` requires are green on each promotion SHA. |
| 86 | +- c-3 — `origin/preview` tip is the preview promotion SHA and its push CI is green. |
| 87 | +- c-4 — `origin/main` tip is the stable promotion SHA and its push CI is green. |
| 88 | +- c-5 — npm shows `latest=2.39.0` and `preview=2.39.0-preview.20260901`, each |
| 89 | + `gitHead` matching its promotion SHA. |
| 90 | + |
| 91 | +## Out of scope |
| 92 | + |
| 93 | +Merging any of the 20 open feature/fix PRs. Rewriting `dev` history. Touching product |
| 94 | +code absent a confirmed blocker. Running the full local suite — hosted exact-SHA CI is |
| 95 | +the primary evidence surface for this unit. |
0 commit comments