| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
Grant id-token write permission, upgrade npm to a version that supports trusted publishing, and drop NPM_TOKEN so semantic-release authenticates to the registry via OIDC instead of a long-lived token. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
|
🎉 This PR is included in version 4.3.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Summary
The release workflow currently fails to publish to npm because it still authenticates with NPM_TOKEN instead of using the trusted publishing (OIDC) configuration set up on npmjs.com. See the failing run: https://github.com/commitizen/cz-cli/actions/runs/27391262960/job/80976026728
Three things were needed to make OIDC actually take over:
Test plan