Publish version-less stable-name download aliases - #45
Merged
Conversation
…kage dish-amd64.deb, dish-x86_64.rpm, Dish-x86_64.AppImage and Dish-x86_64.flatpak are now uploaded alongside the versioned files, so releases/latest/download/<name> is a permanent link to the newest build, matching latest.json which already worked that way. The repo landing page's AppImage instructions use the stable link instead of a placeholder filename the reader had to fill in. The aliases are staged before the harden job, so SHA256SUMS, the cosign signatures and the SLSA provenance cover them.
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
1 participant
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.
What
Every package job now uploads its artifact twice: the versioned name (unchanged) plus a version-less stable name:
dish-amd64.debdish-x86_64.rpmDish-x86_64.AppImageDish-x86_64.flatpakreleases/latest/download/<name>is therefore a permanent link to the newest published build — the same contractlatest.jsonalready relies on, and the same one dish-windows ships fordish-setup.exe. This lets dish-website (and the gh-pages landing page) link "the latest build" without a rebuild per release.The aliases are staged inside each build job, so the shared harden job covers them with SHA256SUMS, cosign keyless signatures, and SLSA provenance like every other asset. No
.zsync/.sha256aliases: AppImageUpdate matches the versioned pattern, and SHA256SUMS covers the alias.Also
curl -fLOof the stable link instead of aDish-X.Y.Zplaceholder the reader had to fill in from the releases page.The workflow header and CHANGELOG document the stable names as a public API: once linked, renaming one silently breaks downloads in the field.