Repository navigation
ci: run npm publish on self-hosted Mac minis - #14
Merged
Merged
Conversation
Move the remaining GitHub-hosted publish job onto the Mac mini runners. npm trusted publishing does not support self-hosted runners, so authenticate with an NPM_TOKEN secret and keep the existing pack, dry-run, and auth checks. Co-authored-by: Joe Blau <[email protected]>
joeblau
marked this pull request as ready for review
October 18, 2026 17:33
This was referenced Oct 18, 2026
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 loses npm trusted publishing and provenance. Official npm docs say trusted publishing supports GitHub-hosted runners only; self-hosted runners are not supported (Trusted publishing for npm packages). This PR still moves the last GitHub-hosted job onto the Mac minis, but it authenticates with a long-lived
NPM_TOKENinstead of OIDC. Joe needs to add anNPM_TOKENrepository secret with publish rights for@bloxwap/fontbefore the next release, and can reject this tradeoff if keeping trusted publishing onubuntu-latestis preferred.What changed
publishnow usesruns-on: [self-hosted, macOS, ARM64](same labels as the other jobs; runner group JWS)..github/scripts/macos-python313.shagain.actions/setup-pythoncannot install on these minis (/Users/runneris not writable).NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}.id-token: writeis removed because OIDC trusted publishing cannot work here.check-publish-auth.mjsstill runs on every release, including when the version is already published. It now checks the token (whoami + collaborator write access) and never prints it.npm publish --dry-run --force, npm>=11.5.1, fonttools/brotli pins, and the skip-if-published gate are unchanged.Docs
docs/ci-runners.mdnow says every job is on the minis, and that publish usesNPM_TOKENwithout provenance.Do not merge until Joe decides whether this token fallback is acceptable.