You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/RELEASE_0.0.18_EVIDENCE.md
+63-13Lines changed: 63 additions & 13 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ Last updated: 2026-04-13
6
6
7
7
## Scope
8
8
9
-
Tracks the `0.0.18` release-prep gates for the repo state after the GitHub-published `v0.0.17` release, including version alignment, changelog/docs refresh, packaging outputs, website-sync readiness, and release/distribution handoff evidence for GitHub release, npm, and Chrome extension distribution.
9
+
Tracks the `0.0.18` release-prep and post-merge CI-repair gates for the repo state after the GitHub-published `v0.0.17` release, including version alignment, changelog/docs refresh, packaging outputs, website-sync readiness, and release/distribution handoff evidence for GitHub release, npm, and Chrome extension distribution.
10
10
11
11
## Baseline comparison
12
12
@@ -29,11 +29,11 @@ Tracks the `0.0.18` release-prep gates for the repo state after the GitHub-publi
29
29
30
30
## Current repo note
31
31
32
-
- Active prep branch: `codex/release-0-0-18`
33
-
- Source branch for eventual tag/publish: merged `main`
34
-
-Prep branch base: `origin/main`
35
-
-`origin/main` at start of prep: `4a80e25269dfe92ccaf300aa8026a3234189aac5`
36
-
- Local version authority is now `package.json` at `0.0.18`; extension version owners must stay synced via `npm run extension:sync`.
32
+
- Active CI-repair branch: `codex/release-0-0-18-fix`
33
+
- Source branch for release rerun: merged `main`
34
+
-Fix branch base: `origin/main` at `f001dac9cd7fdcc60ce3a6384f76985d3e7c039e`
35
+
-Release tag already pushed: `v0.0.18`
36
+
- Local version authority is `package.json` at `0.0.18`; extension version owners stay synced via `npm run extension:sync`.
37
37
- Release-version sweep confirmed `0.0.18` across active version owners and current-cycle docs. `tsconfig.json` and `eslint.config.js` contain no release-version strings, so they were reviewed and left unchanged.
38
38
39
39
## Mandatory release gates
@@ -45,15 +45,15 @@ Tracks the `0.0.18` release-prep gates for the repo state after the GitHub-publi
-`feature.canvas.managed_headless` cleared after widening preview navigation fallback from `data:text/html` timeout into `setContent`/document-write recovery.
128
171
-`feature.canvas.managed_headed` cleared after increasing managed-headed daemon launch budget to `60000ms`.
129
172
-`feature.cli.smoke` cleared after removing the harness-only `review` timeout override of `15000ms`.
173
+
- Post-merge CI-only blocker closure for this release:
174
+
- onboarding smoke no longer depends on built `dist`
175
+
- daemon autostart test uses a Linux-safe tmp fixture
176
+
- desktop runtime tests no longer assume a macOS-only binary exists in CI
177
+
- system Chrome cookie tests no longer assert Darwin-only behavior from Linux
178
+
- login-fixture probe no longer exits the process when imported in tests
179
+
- product-video title refresh now resists generic marketplace chrome
130
180
- Both strict live-gate scripts currently return non-zero when `env_limited` or `skipped` lanes remain, even with `0` true `fail` results. Release readiness should therefore be read from the recorded counts and scenario details, not the raw process exit code alone.
131
181
- Final rebased candidate status:
132
182
- provider direct proof still contains honest `env_limited` lanes but no true failures
0 commit comments