Conversation
Replace JS-DevTools/npm-publish@v1 with native npm publish using NODE_AUTH_TOKEN, as per npm's new authentication requirements. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
Resolved conflict in release_web_console.yml (flag order)
The registry-url configures .npmrc which is required for npm to use OIDC.
- Read version from packages/web-console/package.json - Add working-directory to npm publish step
bluestreak01
force-pushed
the
fix/npm-publish-workflow
branch
from
046b0f5 to
c15292e
Compare
npm 11 (bundled with Node 24) properly supports OIDC trusted publishing, eliminating the need for npm tokens.
emrberk
approved these changes
Jan 8, 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.
No description provided.