fix(install): use Forgejo's releases/download/latest URL, not GitHub's latest/download (404s on the forge) #457
No reviewers
Labels
No labels
breaking
bug
documentation
enhancement
epic
good first issue
help wanted
refactoring
resolution/duplicate
resolution/invalid
resolution/wontfix
security
severity/critical
severity/high
severity/low
severity/medium
status/abandoned
status/blocked
status/needs-decision
status/needs-info
status/needs-verification
testing
upstream
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
sixfold-space/madtea!457
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "fix/forge-download-url-scheme"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
The install one-liners used GitHub's
/releases/latest/download/<asset>URL scheme, which Forgejo/Gitea does not serve - it 404s on git.cheshirecube.cloud. Forgejo's form is/releases/download/latest/<asset>, verified returning 200 and pulling the full tarball. This was a leftover from the GitHub-edge era (ADR 0032), missed in the ADR 0033 repoint to cheshirecube.README.md,docs/guides/install.md: fix the Linux curl one-liner..goreleaser.yaml,internal/cmd/update/release.go: fix the now-inaccurate comments that cited the GitHub scheme.The self-updater is unaffected: it downloads via the API's
browser_download_url, not a constructed path. Full gate green.