Revert npm publish workflow runner to ubuntu-latest#54
Merged
coleaeason merged 1 commit intomainfrom Feb 12, 2026
Merged
Conversation
Blacksmith runners are classified as self-hosted, which causes npm publish --provenance to fail with E422 because npm's Sigstore provenance verification requires GitHub-hosted runners. Co-authored-by: Andrew Gable <[email protected]>
coleaeason
approved these changes
Feb 12, 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
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.
Details
Reverts
runs-onfor the npm publish job fromblacksmith-2vcpu-ubuntu-2404back toubuntu-latest.Blacksmith runners are classified as
"self-hosted"by GitHub Actions, butnpm publish --provenancestrictly requires"github-hosted"runners for Sigstore provenance verification. This causes an E422 error when any Expensify npm package tries to publish:This single change fixes publishing for all repos that call this reusable workflow:
react-native-wallet, react-native-onyx, react-native-live-markdown, expensify-common, eslint-config-expensify, react-native-qrcode-svg, react-native-key-command, react-native-x-maps, react-native-x-draggable-list, and react-native-x-geolocation.
Related Issues
https://github.com/Expensify/Expensify/issues/599808
Manual Tests
Merge this PR and verify that npm publish succeeds on one of the affected repos (e.g., push a change to react-native-wallet main and confirm the publish workflow completes without E422).
Linked PRs
N/A - no downstream changes needed. All affected repos reference
npmPublish.yml@mainso they pick up this fix automatically.