ci(release): run npm publish on github-hosted runner for provenance#5312
Merged
Conversation
npm provenance verification rejects Blacksmith runners with E422
("Unsupported GitHub Actions runner environment: self-hosted"); only
github-hosted runners are accepted by sigstore for provenance
attestations.
Move the publish job back to ubuntu-latest. The job is short and not
compute-bound, so the wall-clock cost is negligible. publish-homebrew and
publish-scoop don't go through npm provenance and stay on Blacksmith.
… runner Match the publish job and keep all publish-* jobs on ubuntu-latest. These jobs only push small commits to the homebrew-tap and scoop-bucket repos, so the wall-clock cost of a github-hosted runner is negligible and not worth the Blacksmith optimization.
jgoux
approved these changes
May 20, 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
3 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.
The release workflow's
publishjob was migrated to a Blacksmith runner in #5300, which broke npm publish:publish.tspasses--provenancetopnpm publish, which has sigstore attest the build against the runner's OIDC identity. Blacksmith runners present asself-hostedto sigstore, so npm rejects the upload with E422.Move only the
publishjob back toubuntu-latest.buildandsmoke-teststay on Blacksmith;publish-homebrewandpublish-scoopdon't go through npm/sigstore (they push to the tap/bucket repos via git) and also stay on Blacksmith. The publish job is short and not compute-bound, so the wall-clock cost of github-hosted is negligible.Failed run that motivated this: https://github.com/supabase/cli/actions/runs/26153946606
Generated by Claude Code