Update the Cirrus Rolling binaries upload token, which had expired.
Some context, for anyone wanting to know more about this:
(Note for context, in case anyone is wondering and is unclear how we set these up: For convenience reasons, this is a fine-grained PAT with just the needed permissions for pulsar-rolling-releases repo, generated on my personal GitHub account. The PAT could just as well be made on anyone's account with adequate permissions to the pulsar-rolling-releases repo. We could further jump through some hoops to make a "GitHub App" to be able to auth as the app or as the org or whichever it is instead, but it appears, to put it mildly, to be a huge hassle and without a whole lot of benefit. So, going to keep doing this as a PAT for now.)
(Second note for more context: I already updated the GitHub Actions Rolling token, which I can do in the settings UI for this repo here on GitHub.com, and doesn't require any changes to repo files, so it didn't need a PR. Updating the Cirrus rolling upload token requires updating .cirrus.yml, and so requires a PR (e.g. this PR) to get that changed file into the repo.)
Update the Cirrus Rolling binaries upload token, which had expired.
Some context, for anyone wanting to know more about this:
(Note for context, in case anyone is wondering and is unclear how we set these up: For convenience reasons, this is a fine-grained PAT with just the needed permissions for pulsar-rolling-releases repo, generated on my personal GitHub account. The PAT could just as well be made on anyone's account with adequate permissions to the pulsar-rolling-releases repo. We could further jump through some hoops to make a "GitHub App" to be able to auth as the app or as the org or whichever it is instead, but it appears, to put it mildly, to be a huge hassle and without a whole lot of benefit. So, going to keep doing this as a PAT for now.)
(Second note for more context: I already updated the GitHub Actions Rolling token, which I can do in the settings UI for this repo here on GitHub.com, and doesn't require any changes to repo files, so it didn't need a PR. Updating the Cirrus rolling upload token requires updating
.cirrus.yml, and so requires a PR (e.g. this PR) to get that changed file into the repo.)