Fix npm publish github action#349
Merged
Merged
Conversation
|
🚀 Preview: https://pr-349--openscan.netlify.app |
josealoha666
approved these changes
Mar 26, 2026
josealoha666
left a comment
josealoha666
left a comment
Collaborator
There was a problem hiding this comment.
LGTM — straightforward bump of actions/checkout and actions/setup-node from v4 → v5.
AugustoL
approved these changes
Mar 26, 2026
11 tasks
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.
Description
Fix npm publish CI workflow failing with ENEEDAUTH by bumping GitHub Actions to v5, matching the working workflows in other openscan repos.
Related Issue
Fixes failing Publish to npm workflow run.
Type of Change
Changes Made
Screenshots (if applicable)
Checklist
npm run format:fixandnpm run lint:fixnpm run typecheckwith no errorsnpm run test:runAdditional Notes
The v5 versions properly support OIDC (Trusted Publishing) for npm authentication. The v4 versions were not wiring the OIDC token correctly, causing ENEEDAUTH errors during npm publish. This aligns the explorer workflow with the working workflows in network-connectors, hardhat-plugin, and explorer-metadata.
The other openscan repos (network-connectors, hardhat-plugin, explorer-metadata) already use v5 for both actions and publish successfully with OIDC authentication.