Repository navigation
Generate website downloads and update feed from published releases - #418
Merged
Merged
Conversation
This was referenced Nov 9, 2026
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 website and desktop update feed currently require manual version/URL edits, and publishing a release does not refresh the site. A new release can leave old downloads advertised or falsely imply the PPA advanced with GitHub.
Generate the catalog, compatible schema-1
/version.jsonfeed and current checksum copies from the highest numeric published stable Holder release. Require unique complete platform assets, verify checksum files against GitHub asset digests, and verify the Linux checksum signature against the committed public key. An incomplete newest release fails generation rather than falling back to an older release. Preserve the Windows development label and keep PPA status/version independently declared in_data/ubuntu.json(carried forward as 0.2.5).Remove redundant committed current-release data and hardcoded page version labels; retain historical checksum URLs. Update download detection tests to use generated data. Stable-release publication dispatches the website workflow on
main, matching the live Pages environment’s main-only deployment rule; the dispatcher alone gainsactions: writeto start that run. Push/manual deployment remains available. No environment settings are changed. Update the runbook with generation, PPA and retry procedures.Validation: all 33 release tests and 41 staging tests pass, including complete/incomplete/ambiguous/prerelease cases, checksum/digest failures, the real public signature and modified-checksum rejection. Live generation against published 0.2.5 passes. Jekyll builds and browser download-detection tests pass for both real 0.2.5 data and a future 0.2.6 fixture (production Windows pattern, older 0.2.5 PPA and
/previewbase path). Boundary, version, YAML and diff checks pass. Site deployment and the publication dispatcher will be observed after merge / the next actual release; no site was deployed or release published during local validation.Continues #110 and #122. Root development
VERSIONremains 0.2.6; the public feed continues to advertise the actually published 0.2.5 release.