@@ -65,10 +65,45 @@ gh run view 32355161140 -> success @ 584059132
6565A pushed commit and a dispatched workflow were not treated as a completed release; each artifact
6666above was read back from its own authority.
6767
68- ## Not done
68+ ## The preview channel, published after this record was first written
6969
70- The preview channel carries ` 2.28.0-preview.20260820 ` as a commit, but npm ` dist-tags.preview `
71- still reads ` 2.26.0-preview.20260819 ` — that channel has not been published. Its CI was still
72- in progress at ` d2c700c1a ` . Stable was the release under authorization; the preview publish is
73- a separate decision.
70+ At the time the section above was written, ` preview ` carried the version commit but npm still
71+ read ` 2.26.0-preview.20260819 ` — the channel had been trailing ` latest ` by a full release. It
72+ has since been published on the same path.
7473
74+ | Artifact | Value |
75+ | ---| ---|
76+ | Release commit | ` d2c700c1a ` (preview) |
77+ | Tag | ` v2.28.0-preview.20260820 ` |
78+ | GitHub release | ` v2.28.0-preview.20260820 ` , pre-release, 2026-08-20T10:54:38Z |
79+ | Release workflow | run ` 32361122670 ` , ** success** |
80+ | npm dist-tags | ` preview: 2.28.0-preview.20260820 ` |
81+
82+ Both channels now sit on the same content, which is what ` preview ` is for and what it had
83+ stopped being while it lagged a release behind.
84+
85+ The helper enforces the channel pairing itself rather than trusting the invocation: a
86+ ` preview ` branch release must carry a ` -preview. ` version and publish to the ` preview `
87+ dist-tag, and ` main ` must be stable semver on ` latest ` . There is no argument combination that
88+ crosses them.
89+
90+ ** The last dispatch of this publish failed, and that failure is the guard working.** Run
91+ ` 32361621459 ` refused with "v2.28.0-preview.20260820 already exists. Refusing to publish a
92+ version with pre-existing Git metadata." A local shell had died mid-suite and the release was
93+ restarted; by then run ` 32361122670 ` had already published. The refusal is what turned a
94+ possible double-publish into a no-op, and it is the same preflight that caught the stable
95+ re-run described above.
96+
97+ ## Two Linux failures that were not defects
98+
99+ ` test 1/4 ` failed twice on `Codex autostart shim > an aged lock held by a live restore owner
100+ is never reclaimed`, once on the stable release PR and once on the preview one. Both times it
101+ hit the 60 s lane ceiling; both times it passed on re-run, and it passes locally in a 20 s
102+ single-file run. The case spawns two real Bun processes and has one wait for the other's lock,
103+ so it is spawn-latency-bound on a contended runner rather than assertion-bound. It carries no
104+ budget of its own, unlike the cases in ` tests/helpers/test-budget.ts ` .
105+
106+ Worth naming rather than burying: two occurrences on the same case is a pattern, not noise. It
107+ is not a release blocker — nothing about the shipped code changed between the red and green
108+ runs — but it belongs on the same list as the Windows spawn-cost failures in #2152 , and giving
109+ it an intrinsic budget is the obvious next step.
0 commit comments