feat(release): a launcher release page links its files through git-cdn.magicbean.dev #19
No reviewers
Labels
No labels
area/build
area/install
area/saves
area/ui
area/updates
good first issue
gpu/amd
gpu/intel
gpu/nvidia
help wanted
kind
bug
kind
chore
kind
docs
kind
feature
kind
performance
kind
question
platform/linux
platform/steam-deck
platform/windows
priority
critical
priority
high
priority
low
status
blocked
status
confirmed
status
duplicate
status
invalid
status
needs-info
status
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
MagicBeanDev/LongshotLauncher!19
Loading…
Reference in a new issue
No description provided.
Delete branch "HumanBean/LongshotLauncher:release/page-cdn"
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?
Why
A launcher release page's download buttons pointed at git.magicbean.dev, which sends the file from R2's regional endpoint; git-cdn.magicbean.dev serves the same paths from Cloudflare's edge, cached.
What changed
scripts/release.py:CDN = "https://git-cdn.magicbean.dev"; the launcher's page header (page_header) links its installer, AppImage and portable zip there. Longshot's header is unchanged (it links longshot.magicbean.dev, whose redirects already go to git-cdn).tests/test_release.py,docs/releases.md: to match. The four shared files stay byte-identical with MagicBeanDev/Longshot (same PR there).Flags and settings
None
Measurements
main:
a799805f(2026-11-13)this PR: release/page-cdn @
393b2d3ea799805f393b2d3eTesting
Tested:
tests/test_release.py; the four shared files identical (cmp).Not tested: a release run; the next launcher release shows it.
Needs other testers: None
Screenshots
Nothing on screen
Risk and rollback
If git-cdn were down, a player clicking the page would get an error instead of the file (the launcher's own downloads fall back; a page link can't). Reverting the commit is enough.
Checklist
For everyone
type(scope): description).main.python -I -B tests/run_all.pyrun and passing (any failure that also fails onmainis named above).third_party/untouched (a new folder with aPROVENANCE.mdinstead).