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.34_EVIDENCE.md
+20-8Lines changed: 20 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,6 @@
1
1
# v0.0.34 Release Evidence
2
2
3
-
Status: prepared
3
+
Status: npm and GitHub released; Chrome Web Store manual handoff pending
4
4
Target release date: 2026-05-22
5
5
Target tag: `v0.0.34`
6
6
@@ -10,8 +10,9 @@ Tracks the `0.0.34` release cycle for the Inspired Design harvest recovery follo
10
10
11
11
Current status note:
12
12
- Source version metadata is aligned from `0.0.33` to `0.0.34`.
13
-
- npm and GitHub release publication are planned through the public release workflow.
14
-
- Chrome Web Store publication is planned as a manual browser-gated lane for this release.
13
+
- npm package `opendevbrowser@0.0.34` is published.
14
+
- GitHub release `v0.0.34` is published with extension assets.
15
+
- Chrome Web Store publication remains a manual browser-gated lane because Chrome Web Store developer pages cannot be scripted and this repo has no `CWS_*` secrets configured for API publication.
15
16
16
17
## Reference State
17
18
@@ -94,12 +95,23 @@ Current status note:
94
95
95
96
## External Release Workflow Evidence
96
97
97
-
- Pending tag-driven release workflow.
98
-
- Pending npm publish verification.
99
-
- Pending registry consumer smoke.
100
-
- Pending GitHub release verification.
101
-
- Pending Chrome Web Store manual publish evidence.
-[x] Tag-driven release workflow result: failed at `Publish npm package`; earlier release metadata, checkout, install, version alignment, release quality gates, extension packaging, and checksum generation passed. npm returned `E404` while publishing `opendevbrowser@0.0.34` from the repository token.
100
+
-[x] Local npm publish fallback: `npm publish --access public --loglevel warn` completed successfully from `main` at tag `v0.0.34` after `version:check`, `build`, and `extension:build`.
101
+
-[x] npm publish verification: `npm view opendevbrowser version dist-tags dist.tarball dist.integrity --json --cache /tmp/npm-cache-odb-release-034-final --prefer-online` returned version `0.0.34`, `latest` dist-tag `0.0.34`, tarball `https://registry.npmjs.org/opendevbrowser/-/opendevbrowser-0.0.34.tgz`, and integrity `sha512-SG7TSv4bO4EEpUHdzntFaNrsad7x5eJm7OvT/HuQ4zM5zLsrKtx4SYetDeBw+Tqeef+AAH6K8mhNtzQvqJsa+Q==`.
102
+
-[x] Registry consumer smoke: `npm_config_cache=/tmp/npm-cache-odb-release-034-smoke node scripts/registry-consumer-smoke.mjs --version 0.0.34 --output artifacts/release/v0.0.34/registry-consumer-smoke.json` passed with `success: true`, `installAttempts: 1`, `helpAliasMatches: true`, `findItFastPresent: true`, `extensionDirExists: true`, `skillsDirExists: true`, and `versionMatches: true`. The first immediate smoke attempt failed during npm propagation with stale cached `0.0.33` metadata, then passed with an isolated npm cache after registry metadata exposed `0.0.34`.
-[x] GitHub release-only workflow result: passed in `4m51s`; release metadata, checkout, install, version alignment, full release quality gates, extension packaging, checksum generation, and GitHub release publication passed. npm publish and registry smoke were intentionally skipped because npm had already been published locally and verified by local consumer smoke.
-[x] GitHub release verification: `v0.0.34` is not draft, not prerelease, published at `2026-05-22T19:10:38Z`, target commitish `main`.
107
+
-[x] GitHub release asset verification: downloaded `opendevbrowser-extension.zip` and `opendevbrowser-extension.zip.sha256` to `/tmp/opendevbrowser-release-v0.0.34-assets`; `shasum -a 256 -c opendevbrowser-extension.zip.sha256` returned `opendevbrowser-extension.zip: OK`.
-[ ] Chrome Web Store manual publish evidence: pending user completion in Chrome Web Store Developer Dashboard.
111
+
-[x] Chrome Web Store manual lane preflight: local env has no `CWS_*` variables, `gh secret list --repo freshtechbro/opendevbrowser` lists no `CWS_*` secrets, and API/workflow publication is unavailable without those credentials.
112
+
-[x] Chrome Web Store dashboard handoff: Chrome extension-backed browser reached `https://chrome.google.com/webstore/devconsole/ca194bec-a1d3-46ce-90f0-1c2fd8ab9a71/mfajibjdacmecipgcpnagccbieabglhk/edit/package?pli=1` with title `Package Information`, but Chrome Web Store pages return `The extensions gallery cannot be scripted`. The in-app browser redirected to Google sign-in for Chrome Web Store. Manual upload should use `/tmp/opendevbrowser-release-v0.0.34-assets/opendevbrowser-extension.zip`.
102
113
103
114
## Notes
104
115
105
116
- Strict live gates are separate from release quality gates and are deferred unless specifically run.
117
+
- GitHub Actions emitted the existing Node.js 20 action deprecation warning for `actions/checkout@v4`, `actions/setup-node@v4`, and `softprops/action-gh-release@v2`; this is a follow-up maintenance item, not a `v0.0.34` release blocker.
0 commit comments