chore: updates workflow to enable npm trusted publishing - #451
Merged
Conversation
jwndlng
marked this pull request as draft
October 27, 2025 08:44
jwndlng
marked this pull request as ready for review
October 27, 2025 10:16
ilbertt
suggested changes
Oct 27, 2025
ilbertt
suggested changes
Oct 27, 2025
Contributor
|
Commitizen is checking all the commits in this PR, and it's not happy about 945f17e. Can you try squashing them into one, conventional commits-compliant, commit? |
jwndlng
force-pushed
the
jwndlng-patch-1
branch
from
October 27, 2025 14:12
d5ec280 to
493be06
Compare
Member
Author
|
Squashed all commits. Check succeeds now. |
ilbertt
approved these changes
Oct 27, 2025
jwndlng
enabled auto-merge (squash)
October 27, 2025 14:20
jwndlng
disabled auto-merge
October 27, 2025 14:20
jwndlng
enabled auto-merge (squash)
October 27, 2025 14:24
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.
NPM package publishing will be migrated to use Trusted Publishing (via OIDC).
To ensure security and restrict access, we will configure the OIDC token request to only be available to jobs running in the dedicated 'release' environment. This environment will be a required condition for obtaining the necessary NPM token.
Changes:
Set node version to 24, which includes npm v11Separate PR.id-tokenpermission required for creating JWTreleasefor obtaining the short-lived tokensncipollo/release-actionto commit SHA