Conversation
gyuheon0h
approved these changes
Feb 12, 2026
Overall package sizeSelf size: 37 MB Dependency sizes| name | version | self size | total size | |------|---------|-----------|------------|🤖 This report was automatically generated by heaviest-objects-in-the-universe |
gyuheon0h
pushed a commit
that referenced
this pull request
Feb 12, 2026
Merged
gyuheon0h
added a commit
that referenced
this pull request
Feb 12, 2026
gyuheon0h
pushed a commit
that referenced
this pull request
Mar 3, 2026
Merged
gyuheon0h
pushed a commit
that referenced
this pull request
Mar 3, 2026
gyuheon0h
pushed a commit
that referenced
this pull request
Mar 3, 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.
What does this PR do?:
release.ymlso it works well with OIDC release method.Motivation:
Npm no longer allows releasing with broad tokens. It still allows releasing with granular tokens, but their lifetime is limited now. This all makes releasing while authenticating with tokens painful. OIDC provides a much better way to release the packages, and will be the preferred way going forward.
OIDC needs to be enabled for this repo in the Npm settings – I just did that. After that, publishing is rather simple, it no longer requires a token, but rather depends on GitHub proving to Npm that the release request came from a GH action as configured (we need to specify the organization, repo name, filename with the release action, and the release environment in the NPM configuration.)
Additional Notes:
Node.js 24 is used explicitly for releasing so we have a recent version of
npmCLI. The token is removed from the release, the only thing required for OIDC to work from the GH side is a write permission toid-tokenin the action.Jira: PROF-12794