Skip to content

Commit 7f4e08d

Browse files
committed
docs(devlog): record the executed publish
1 parent 0de0204 commit 7f4e08d

1 file changed

Lines changed: 18 additions & 0 deletions

File tree

‎devlog/_plan/260901_release_train_2390/040_wp4_publish.md‎

Lines changed: 18 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -50,3 +50,21 @@ tree was published, and is a stop-everything condition.
5050
preview CI failed (unit `000`). Publishing `2.39.0-preview.20260901` moves the tag
5151
forward and closes that gap; 2.38.0-preview is skipped rather than backfilled, which
5252
matches how the previous-tag baseline in `release.yml` already computes its range.
53+
54+
## Executed
55+
56+
Preview dispatch: run `33464064409`, success, `expected-sha=75f3895c1…`.
57+
Stable dispatch: run `33464579658`, success, `expected-sha=af6113a03…`.
58+
59+
```
60+
npm view @bitkyc08/opencodex dist-tags --json
61+
{ "latest": "2.39.0", "preview": "2.39.0-preview.20260901" }
62+
```
63+
64+
`gitHead` for `2.39.0` is `af6113a0381d6fff2e4dce587652825c7eeb6423`; for
65+
`2.39.0-preview.20260901` it is `75f3895c14965205be694e8ebb8e93f472630539`. Both match
66+
their promotion SHAs exactly, which is the check that distinguishes a published package
67+
from a merged branch. GitHub releases `v2.39.0` and `v2.39.0-preview.20260901` exist.
68+
69+
The stale preview channel is closed: it moved from `2.36.0-preview.20260830` to
70+
`2.39.0-preview.20260901` in one step.

0 commit comments

Comments
 (0)