Skip to content

Recover verified updates when GitHub API returns 404 - #3

Merged
iMumd merged 1 commit into
mainfrom
fix/update-metadata-fallback
Oct 30, 2026
Merged

iMumd merged 1 commit into
mainfrom
fix/update-metadata-fallback

Conversation

@iMumd

@iMumd iMumd commented Oct 30, 2026

Copy link
Copy Markdown
Owner

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

  • npm test: 22 tests plus rule-worker checks pass locally.
  • The exact Bash HTML parser was exercised against live GitHub: all 10 asset digests match the API for v1.0.2.
  • Windows fixture simulates API 404 and verifies correct Setup selection without downloading/running an installer; passed locally in Windows PowerShell.
  • Linux integration now simulates API 404, completes replacement via the public page, then rejects a tampered archive.
  • Bash and PowerShell syntax checked. All platform CI must pass before merge.

No version bump or release publication. Self-review, not independent approval.

@iMumd

iMumd commented Oct 30, 2026

Copy link
Copy Markdown
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.

@iMumd
iMumd merged commit c6d4dd8 into main Oct 30, 2026
3 checks passed
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