Remove legacy npm nightly token workflow - #2797
Merged
Merged
Conversation
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.
What changed
npm-nightlyjob from the manual daily workflowcidependency on that publishing jobWhy
The npm package now uses the separately proven stage-only trusted publisher workflow, and the legacy
NPM_TOKENsecret has been deleted. Keeping a dormant direct-token publisher would leave a misleading, unusable release path in the repository.Impact
Manual daily CI remains available and runs directly. This change does not publish or stage an npm package.
Validation
.github/workflows/daily.ymlwith Ruby/Psychgit diff --checkNPM_TOKENornpm-nightly