ci(release-please): Enable trusted publishing#876
Merged
Conversation
Using trusted publishing via OIDC for npm publishing. This makes the use of npm tokens obsolete and improves security. See: https://docs.npmjs.com/trusted-publishers
Member
|
Just a note for future readers: Using the trusted publishing concept of npm automatically enforces the usage of the provenance functionality. Therefore passing the "--provenance" flag is no longer required. See: https://docs.npmjs.com/trusted-publishers#automatic-provenance-generation |
d3xter666
approved these changes
Sep 25, 2025
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
3 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.
Using trusted publishing via OIDC for npm publishing. This makes the use of npm tokens obsolete and improves security.
See: https://docs.npmjs.com/trusted-publishers
JIRA: CPOUI5FOUNDATION-1127