Repository navigation
Update feed: never serve an older release because the GitHub API was busy - #222
Merged
Merged
Conversation
…busy Without a token the API refuses after 60 calls an hour, and the feed then answered with the last known release, kept for a week. After v0.2.22 the desktop apps kept seeing 0.2.20 and found no update. Now github.com's latest-release redirect (no API quota) says which release is the latest; the kept copy answers only while it is still that one.
… (it failed when an earlier test's one came due at that hour)
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.
After v0.2.22 was published, https://usegodmode.com/api/update/latest.json kept answering 0.2.20 for hours, so the desktop apps found no update (Tauri uses the first update endpoint that answers). The Worker has no GITHUB_TOKEN; when the API refuses (60 calls an hour per Cloudflare IP),
latestReleasereturned the last known release, kept for a week.Now github.com's latest-release redirect (no API quota) says which release is the latest; the kept copy answers only while it is still that one, otherwise the release is read from the public release pages.
Already deployed on its own on top of the live version c875b57 (worker 15b7a4b2), so the undeployed #200/#203 stay undeployed; verified: the feed serves 0.2.22, the bundle redirects to the GitHub download.
astro check: 0 errors.