Skip to content

ci: the release gate verifies the upstream tag with the job's token, as ci.yml does - #9

Merged
Sunrisepeak merged 1 commit into
mainfrom
ci/release-token
Nov 22, 2026
Merged

Sunrisepeak merged 1 commit into
mainfrom
ci/release-token

Conversation

@Sunrisepeak

Copy link
Copy Markdown
Member

In release.yml, the step "Verify immutable upstream release mapping" runs tools/check_release.py, which runs tools/import_upstream.py --verify-tag. That script reads the GitHub API with GITHUB_TOKEN when the variable is set. ci.yml sets it for the same command; release.yml did not.

Without the token the call used the runner's shared per-address quota. The release of mwrap-b10069.2 (run 45017316991) was refused twice with HTTP Error 403: rate limit exceeded.

This PR sets GITHUB_TOKEN for that step. The tag mwrap-b10069.2 is not moved: its Release job is re-run, and from now on releases read the API with the job's token.

…as ci.yml does

check_release.py runs import_upstream.py --verify-tag, which reads the
GitHub API with GITHUB_TOKEN when it is set. release.yml did not set it, so
the call shared the runner's per-address quota and mwrap-b10069.2's release
was refused twice with "HTTP Error 403: rate limit exceeded".
@Sunrisepeak
Sunrisepeak merged commit 8bd7eeb into main Nov 22, 2026
8 checks passed
@Sunrisepeak
Sunrisepeak deleted the ci/release-token branch November 22, 2026 11:37
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.

1 participant