Skip to content

fix(cerro-torre): pin Alire URL to explicit version (re-apply, closes #13)#21

Merged
hyperpolymath merged 1 commit into
mainfrom
refix/cerro-torre-alire-url
May 3, 2026
Merged

fix(cerro-torre): pin Alire URL to explicit version (re-apply, closes #13)#21
hyperpolymath merged 1 commit into
mainfrom
refix/cerro-torre-alire-url

Conversation

@hyperpolymath
Copy link
Copy Markdown
Owner

Re-applies fix originally squash-merged as #18 and reverted as part of the rescript-ecosystem cleanup. Same content. Closes #13.

GitHub's /releases/latest/download/ redirect requires to be an asset of the current latest release. Alire embeds the version in the asset name, so a hardcoded version under /latest/download/ silently 404s when a new Alire ships.

…load/ (#18)

Closes #13.

GitHub's /releases/latest/download/<filename> redirect only works when
<filename> is an asset of the current latest release. Alire's asset
filenames embed the version (alr-X.Y.Z-bin-...), so the previously
hardcoded `alr-2.0.2-bin-...` filename returns 404 against /latest/
the moment a newer release ships — which has happened (current is 2.1.0).

Switch to the explicit-version URL (releases/download/vX.Y.Z/) which
ALWAYS works for the pinned version, regardless of what 'latest' is.
ARG ALIRE_VERSION=2.1.0 lets downstream override the pin.

Same pattern survives Alire releases without breaking.
@sonarqubecloud
Copy link
Copy Markdown

sonarqubecloud Bot commented May 3, 2026

@hyperpolymath hyperpolymath merged commit 01b7abc into main May 3, 2026
21 of 25 checks passed
@hyperpolymath hyperpolymath deleted the refix/cerro-torre-alire-url branch May 3, 2026 10:31
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.

[container-stack/cerro-torre] Alire download URL pinned to stale 2.0.2 — 404s on /latest/download/

1 participant