Repository navigation
ci: authenticate npm publish with NPM_TOKEN on Mac minis - #32
Merged
Merged
Conversation
npm trusted publishing does not support self-hosted runners, so authenticate the existing Mac mini publish job with the org-level NPM_TOKEN secret and drop OIDC trusted publishing and automatic provenance. Co-authored-by: Joe Blau <[email protected]>
joeblau
marked this pull request as ready for review
October 18, 2026 17:40
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
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 npm 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 job in this repo was already on the Mac minis (
runs-on: [self-hosted, macOS, ARM64], runner group JWS). The remaining problem was the publish job still using OIDC (id-token: writeandnpm publish --provenance), which npm does not support on self-hosted runners.What changed
publishauthenticates withNODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}from the org-levelNPM_TOKENsecret (granular, publish rights for@bloxwappackages, already shared with the open-source repos).id-token: writeis removed from the npm publish job. GitHub Pages deploy still uses OIDC.npm publishno longer passes--provenance.check-publish-auth.mjsruns before publish (whoami + collaborator write access) and never prints the token. The fail-closed unit test runs in Tests and in release validation.Docs
docs/ci-runners.md,.github/RELEASING.md, and the public releasing page now say publish usesNPM_TOKENwithout provenance.Do not merge until Tests and Documentation are green.