fix: use npm trusted publishing - #3
Merged
Merged
Conversation
Greptile SummaryThis PR updates the release workflow to use npm trusted publishing. The main changes are:
Confidence Score: 5/5Safe to merge with minimal risk. The change is narrowly scoped to the release workflow and keeps the required OIDC permission for npm trusted publishing. No files require special attention.
What T-Rex did
|
| Filename | Overview |
|---|---|
| .github/workflows/release.yml | Removes the npm token environment variable from the semantic-release step while retaining the job-level OIDC permission required for npm trusted publishing. |
Reviews (1): Last reviewed commit: "fix: use npm trusted publishing" | Re-trigger Greptile
|
🎉 This PR is included in version 0.1.2 🎉 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
1 participant
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.
Removes the npm token from the release workflow so semantic-release publishes through npm trusted publishing/OIDC.