Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CI: Update Rolling upload token for Cirrus CI #936

Merged
merged 1 commit into from
Mar 7, 2024

Conversation

DeeDeeG
Copy link
Member

@DeeDeeG DeeDeeG commented Feb 20, 2024

This PR updates the token used on Cirrus to upload Rolling release binaries.

(The old token had expired.)

Copy link
Member

@confused-Techie confused-Techie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry I missed this one, easy approval

@confused-Techie confused-Techie merged commit 7d2d876 into master Mar 7, 2024
103 checks passed
@DeeDeeG
Copy link
Member Author

DeeDeeG commented Mar 14, 2024

I must have somehow entered the wrong token.

I had regenerated the token a ton of times worrying that the GitHub.com UI was b0rked, as the token appeared to be "the same" every time it regenerated, but on closer look just the first several characters are the same, the much longer segment of random characters toward the latter end of the token are indeed being updated each time.

But in all that regenerating of tokens, maybe I somehow entered one of the ones that I regenerated over, thus deactivating it???

tl;dr I must have messed up, because the upload script is complaining of an invalid token.

https://github.com/pulsar-edit/pulsar/runs/22441241173

Error: Error status: 401 response body:{"message":"Bad credentials","documentation_url":"https://docs.github.com/rest"}

@DeeDeeG DeeDeeG deleted the CI-update-Cirrus-token branch April 19, 2024 16:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants