Conversation
GitHub and NPM recently introduced tighter security on the publishing process for NPM packages. To use trusted publishing without tokens, we have to slightly change the publishing config. Example config can be found here: https://github.com/semantic-release/semantic-release/blob/c58fe12f90022b4d6c6e34fc0eb0e4f7b21e815a/docs/recipes/ci-configurations/github-actions.md#githubworkflowsreleaseyml-configuration-for-node-projects SREI-3017
molikuner
commented
Jan 22, 2026
commit: |
molikuner
commented
Jan 22, 2026
jonotrujillo
approved these changes
Jan 23, 2026
github-actions bot
pushed a commit
that referenced
this pull request
Jan 23, 2026
## <small>2.49.1 (2026-01-23)</small> * fix(AUT-2298): Bug fix for years that default incorrectly (#568) ([5568a13](5568a13)), closes [#568](#568) * fix(ci): extend GITHUB_TOKEN permissions for release (#571) ([85a6fc6](85a6fc6)), closes [#571](#571) * fix(ci): publishing doesn't work (#570) ([6b5dcd7](6b5dcd7)), closes [#570](#570)
Contributor
|
🎉 This PR is included in version 2.49.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
What
This PR migrates the publishing process to use the Trusted Publishing mechanism.
Why
GitHub and NPM recently introduced tighter security on the publishing process for NPM packages.
More info can be found here: https://github.blog/changelog/2025-09-29-strengthening-npm-security-important-changes-to-authentication-and-token-management/
How
Adjust the release process to use id-tokens from GitHub to authenticate against the npm registry.
Closes #569