Skip to content

Commit e510b04

Browse files
authored
Merge pull request #23 from freshtechbro/codex/release-0-0-19-docs-closeout
docs(release): close out 0.0.19 evidence
2 parents 0002d7d + ab9f8b1 commit e510b04

1 file changed

Lines changed: 27 additions & 18 deletions

File tree

docs/RELEASE_0.0.19_EVIDENCE.md

Lines changed: 27 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -1,12 +1,12 @@
11
# v0.0.19 Release Evidence
22

3-
Status: active release ledger
3+
Status: historical completed release ledger
44
Target release date: 2026-04-13
55
Last updated: 2026-04-13
66

77
## Scope
88

9-
Tracks the `0.0.19` release-prep cycle after the published `v0.0.18` release, including npm registry-consumer smoke hardening, browser-scoped computer-use discoverability updates, the screencast stop-race fix, version alignment, packaging, and release handoff readiness.
9+
Tracks the completed `0.0.19` release cycle after the published `v0.0.18` release, including npm registry-consumer smoke hardening, browser-scoped computer-use discoverability updates, the screencast stop-race fix, version alignment, packaging, and release closeout evidence.
1010

1111
## Baseline comparison
1212

@@ -17,7 +17,7 @@ Tracks the `0.0.19` release-prep cycle after the published `v0.0.18` release, in
1717
- GitHub assets:
1818
- `opendevbrowser-extension.zip`
1919
- `opendevbrowser-extension.zip.sha256`
20-
- Current `0.0.19` delta is based on the post-`v0.0.18` hardening work in `codex/generalfixes`.
20+
- Current `0.0.19` delta is based on the post-`v0.0.18` hardening work that merged from `codex/generalfixes` via PR `#22`.
2121

2222
## Release summary
2323

@@ -28,9 +28,10 @@ Tracks the `0.0.19` release-prep cycle after the published `v0.0.18` release, in
2828

2929
## Current repo note
3030

31-
- Active release-prep branch: `codex/generalfixes`
32-
- Release tag not pushed yet: `v0.0.19`
33-
- npm `latest` still points to `0.0.18`
31+
- Release-prep branch `codex/generalfixes` merged into `main` via PR `#22`
32+
- Release tag pushed: `v0.0.19`
33+
- npm `latest` points to `0.0.19`
34+
- GitHub release published: `https://github.com/freshtechbro/opendevbrowser/releases/tag/v0.0.19`
3435
- Local version authority is `package.json` at `0.0.19`; extension version owners stay synced via `npm run extension:sync`
3536
- `docs/RELEASE_0.0.18_EVIDENCE.md` and `docs/NPM_0_0_18_PARITY_INVESTIGATION.md` remain historical release records
3637

@@ -69,13 +70,12 @@ Tracks the `0.0.19` release-prep cycle after the published `v0.0.18` release, in
6970
- [x] `npm pack`
7071
- produced `opendevbrowser-0.0.19.tgz`
7172
- tarball details: `package size=1.7 MB`, `unpacked size=9.1 MB`, `total files=919`
72-
- [ ] After npm publish, `node scripts/registry-consumer-smoke.mjs --version 0.0.19 --output artifacts/release/v0.0.19/registry-consumer-smoke.json`
73-
- cannot be completed locally before publish because `0.0.19` is not on npm yet
74-
- dry-run proof of the new lane succeeded against current npm `latest` (`0.0.18`):
75-
- `success=true`
76-
- `installAttempts=1`
77-
- `helpLineCount=591`
78-
- consumer graph: `@opencode-ai/plugin@1.4.3`, `ws@8.20.0`, `zod@3.25.76`, nested plugin `zod@4.1.8`
73+
- [x] After npm publish, `node scripts/registry-consumer-smoke.mjs --version 0.0.19 --output artifacts/release/v0.0.19/registry-consumer-smoke.json`
74+
- completed against npm `latest` after publish
75+
- `success=true`
76+
- `installAttempts=4`
77+
- `helpLineCount=594`
78+
- consumer graph: `@opencode-ai/plugin@1.4.3`, `ws@8.20.0`, `zod@3.25.76`, nested plugin `zod@4.1.8`
7979

8080
## Repo sanity checks
8181

@@ -101,16 +101,25 @@ Tracks the `0.0.19` release-prep cycle after the published `v0.0.18` release, in
101101

102102
## External release workflow evidence
103103

104-
- [ ] Release workflow run URL
105-
- [ ] GitHub release URL
106-
- [ ] npm publish verification
104+
- [x] Initial tag-triggered public release run failed because npm publish was enabled without `NPM_TOKEN`
105+
- workflow: `https://github.com/freshtechbro/opendevbrowser/actions/runs/24362526855`
106+
- conclusion: `failure`
107+
- head SHA: `0002d7ddeca8c170cec56cf1d1f97de9604955df`
108+
- [x] GitHub release-only rerun completed successfully
109+
- workflow: `https://github.com/freshtechbro/opendevbrowser/actions/runs/24362731433`
110+
- conclusion: `success`
111+
- head SHA: `0002d7ddeca8c170cec56cf1d1f97de9604955df`
112+
- [x] GitHub release URL
113+
- `https://github.com/freshtechbro/opendevbrowser/releases/tag/v0.0.19`
114+
- [x] npm publish verification
115+
- `npm view opendevbrowser version` returned `0.0.19`
107116

108117
## Review note
109118

110119
- Diff review found no blocking issue in the recorder race fix, registry-consumer smoke lane, release workflow wiring, or the `0.0.19` doc/version cutover.
111120

112121
## Notes
113122

114-
- This ledger is commit-ready release-prep evidence, not publish proof.
115-
- The only mandatory gate still pending is the publish-time registry-consumer smoke for `0.0.19`, which becomes actionable only after tag push and npm publish.
123+
- This ledger now captures completed `0.0.19` release evidence, not only release-prep proof.
124+
- The mandatory publish-time registry-consumer smoke is closed with a successful post-publish run against npm `latest`.
116125
- Keep `docs/RELEASE_0.0.18_EVIDENCE.md` and `docs/NPM_0_0_18_PARITY_INVESTIGATION.md` historical; do not rewrite them as active `0.0.19` guidance.

0 commit comments

Comments
 (0)