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.30_EVIDENCE.md
+26-7Lines changed: 26 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -101,13 +101,32 @@ Tracks the `0.0.30` release cycle for uniform workflow output roots across CLI,
101
101
102
102
## External Release Workflow Evidence
103
103
104
-
-[ ] Release workflow run URL
105
-
-[ ] npm publish verification
106
-
-[ ] Registry consumer smoke
107
-
-[ ] GitHub release URL
108
-
-[ ] GitHub release asset verification
104
+
-[x] Release workflow run URL
105
+
- Initial tag run: `https://github.com/freshtechbro/opendevbrowser/actions/runs/25971173850`
106
+
- Result: quality gates, extension packaging, checksum, and npm publish passed; registry consumer smoke failed before GitHub release because the npm registry had not yet propagated `opendevbrowser@0.0.30` to fresh installs.
- Download verification: `gh release download v0.0.30 --repo freshtechbro/opendevbrowser --pattern 'opendevbrowser-extension.zip*'`, then `shasum -a 256 -c opendevbrowser-extension.zip.sha256`.
126
+
- Result: `opendevbrowser-extension.zip: OK`.
109
127
110
128
## Notes
111
129
112
-
- Strict live gates are separate from release quality gates. They remain deferred for this release unless explicitly enabled.
113
-
- If GitHub Actions npm publication fails despite `NPM_TOKEN` being configured, local authenticated npm publish is available as fallback and must be recorded here.
130
+
- Strict live gates are separate from release quality gates and were deferred for this release.
131
+
-`NPM_TOKEN` was configured and npm publication succeeded in the initial tag-driven workflow.
132
+
- The initial tag-driven workflow failed only because registry consumer smoke ran before npm propagation completed. The registry smoke passed locally after propagation, and the GitHub release was completed through a workflow dispatch with npm publication disabled to avoid republishing the already-live version.
0 commit comments