ci: pass GITHUB_TOKEN to the canary snapshot publish - #63
Open
thymikee wants to merge 1 commit into
Open
Conversation
`changeset version --snapshot` runs the GitHub changelog generator added in #52, which aborts without a token. Every canary publish since then has failed before reaching npm; the last canary on npm predates that change.
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.
The "Publish canary snapshot" step runs
changeset version --snapshot canary, which invokes the GitHub changelog generator added in #52 and aborts without a token:Every canary publish since then has failed before reaching npm, including the one after #59 merged (run 34593231337). The
canarydist-tag still points at0.4.0-canary-20260403134337. The release step already passes the token; this passes the same token to the canary step.