Repository navigation
ci: authenticate npm publish with NPM_TOKEN on Mac minis - #57
Merged
Merged
Conversation
Move the self-hosted release publish job off OIDC trusted publishing. npm trusted publishing does not support self-hosted runners, so publish now uses the organization NPM_TOKEN and no longer requests provenance. Co-authored-by: Joe Blau <[email protected]>
joeblau
marked this pull request as ready for review
October 18, 2026 17:48
Keep #56 testnet harness updates and the NPM_TOKEN publish path (no OIDC trusted publishing or automatic provenance). Co-authored-by: Joe Blau <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This drops OIDC trusted publishing and automatic provenance, per Joe's decision. Official npm docs say trusted publishing supports GitHub-hosted runners only; self-hosted runners are not supported (Trusted publishing for npm packages). Same tradeoff as bloxwap/font#14.
Every other job was already on
runs-on: [self-hosted, macOS, ARM64](runner group JWS) after #54. The remaining problem was the releasepublishjob still requesting OIDC/--provenance, which cannot work on the minis.What changed
publishstays on[self-hosted, macOS, ARM64].NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}(organization secret, granular publish rights for@bloxwappackages).id-token: writeis removed from this job because OIDC trusted publishing cannot work here. GitHub Pages deploy still uses OIDC.npm publishno longer passes--provenance. Registry verification still requires the tested tarball integrity; it no longer requires an attestation URL.check-publish-auth.mjsruns on every gated release, including when the version is already published. It checks the token (whoami, then collaborator write access, or a first-publish 404) and never prints it.BLOXWAP_PUBLISH/npm-releasepublish gate are unchanged.Docs
docs/ci-runners.mdanddocs/releases.mdnow say publish uses the orgNPM_TOKENand does not attach provenance.Do not merge this PR from Actions.