ops(ci): dont fetch NPM_TOKEN from env to support provenance - #4
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Updates the release GitHub Actions workflow to avoid injecting NPM_TOKEN into the Changesets publish step, aligning the workflow with npm Trusted Publishing / provenance requirements where a static token should not be used.
Changes:
- Stop passing
secrets.NPM_TOKENintochangesets/action@v1and instead explicitly setNPM_TOKENto an empty string (per linked Changesets discussion).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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
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.
No description provided.