Harden bootstrapper: resolve releases via redirect, not the rate-limited API - #333
Merged
jp-spotter merged 1 commit intoJul 24, 2026
Conversation
This was referenced Aug 5, 2026
Merged
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
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 bootstrapper resolved the latest release by calling
api.github.com/releases/latest, which is rate-limited to 60 requests/hour per IP when unauthenticated. Shared CI and corporate egress IPs exhaust that quota and get HTTP 403, so installs andself updatefail intermittently.It now resolves the latest tag via the
github.com/releases/latestweb redirect instead, which is not subject to that quota and needs no token. All HTTP GETs also gain a small retry with backoff.Verified against all three callers (install,
self update, and the version-check notification): the return still carriestag_nameandpublished_at, so nothing downstream breaks. The change stays standard-library-only and Python 3.9+, per the bootstrapper's constraints.