Repository navigation
Recover verified updates when GitHub API returns 404 - #3
Merged
Merged
Conversation
Owner
Author
|
Self-review complete. CI run 41045278907 succeeded on Windows, Linux and macOS. Linux integration simulated an API 404, completed a verified replacement using public asset metadata, then rejected a corrupted archive. Windows fallback fixture selected the correct installer without executing it. The live public-page parser matched all 10 v1.0.2 asset digests against the API. Stable tag/repository origin validation and required SHA-256 remain intact. The observed user-side transient 404 itself is not claimed reproduced; the single-source failure mode is now covered. |
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.
Problem
A user observed HTTP 404 immediately after Checking for updates. The public endpoints currently return 200 from the development environment, so the transient/environment-specific failure is not claimed to be reproduced live. The installer previously had a single metadata source and exited on an API error.
Fix
Linux/macOS, Windows and manual in-app checks now fall back to GitHub's public latest-release redirect. Command-line updaters parse the published asset SHA-256 from GitHub's expanded asset page, validate the stable tag and repository path, and retain mandatory checksum validation. No pinned version, third-party mirror, auth token or checksum bypass is introduced. Failure of both metadata sources leaves the installation untouched.
Validation
No version bump or release publication. Self-review, not independent approval.