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
{{ message }}
Repository navigation
Commit 75f7063
Browse filesBrowse the repository at this point in the historyBrowse files
fix: the publishConfig check fails closed; pack:verify launches with a sanitized environment
- release.yml stops when the tarball cannot be read or its manifest does not
parse, instead of treating either as 'no publishConfig'.
- pack:verify drops PYTHONPATH, VIRTUAL_ENV, NODE_PATH and the like from the
installed server's environment, so an undeclared dependency cannot resolve
from the caller's shell.
- RELEASING.md and the release skill say to wait for every build leg to
finish and approve the healthy packages, rather than require all green.
Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>
Signed-off-by: cliffhall <[email protected]>
Copy file name to clipboardExpand all lines: RELEASING.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,7 +54,7 @@ Publishing is triggered by a maintainer **publishing a GitHub Release** whose ta
54
54
55
55
The split is about what runs next to the publish credential. Installing dependencies runs their lifecycle scripts, and a build runs a toolchain; in a job that can mint an OIDC token, any of that code could publish. Here the token only ever sits beside the registry client and SHA-pinned actions. Every action in the build and publish jobs is pinned to a commit SHA, enforced by `npm run verify:action-pins`.
56
56
57
-
The build jobs finish before the publish jobs ask for approval, so **approve the `release` environment only once the build jobs are green**. Their logssay what each package will do.
57
+
The build jobs finish before the publish jobs ask for approval, so **wait for every build leg to finish before approving the `release` environment**, and read their logs: they say what each package will do. A package whose build leg passed is safe to approve. One failed build leg does not hold the others back: approve the healthy packages, and handle the failed one as described under [When a publish fails](#when-a-publish-fails).
58
58
59
59
The **registry-diff guard** is what makes a release idempotent and self-healing. A package whose version is already on the registry is **skipped, not failed**:
0 commit comments