Use previous github token to release to homebrew and scoop #884
Conversation
This file contains 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.
Reviewers
r? @gracegoo-stripe
cc @stripe/developer-products
Summary
After merging #881, I released v1.10.0 to test it out, but it failed to publish to homebrew and scoop: https://github.com/stripe/stripe-cli/runs/6680336742?check_suite_focus=true
I can't give more permissions to the new token, but it turns out I can manually override the token for publishing to homebrew and scoop, so this PR uses the original token for that.
As with the last PR, not sure how to test this other than making another release, so I guess I'll release v1.10.1 next.