build(tools): the build tools download from git-cdn.magicbean.dev, Cloudflare's edge, first

No reviewers

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference

MagicBeanDev/LongshotLauncher!17

HumanBean commented

2026-11-13 07:57:01 +00:00

Owner

Why

Forgejo's packages are now in Cloudflare R2 and git-cdn.magicbean.dev serves them from Cloudflare's edge, so the 500+ MB of build tools a player downloads at first start can come from the edge instead of through Unraid's tunnel.

What changed

docs/releases.md: the tools' first URL is now their git-cdn.magicbean.dev link (MagicBeanDev/Longshot's tools.lock, same PR there). Byte-identical with Longshot's.
No code change: the launcher (Core/ToolsLock.cs, Toolchains) tries tools.lock's URLs in order and follows redirects.

Flags and settings

None

Measurements

main: 0965ad32 (2026-11-13)
this PR: build/tools-cdn @ 3fc3f4e5

	main @ `0965ad32`	this PR @ `3fc3f4e5`
tools.lock's first URL	git.magicbean.dev (through the tunnel)	git-cdn.magicbean.dev (Cloudflare's edge)

Testing

Tested: docs/releases.md identical with Longshot's (cmp).

Not tested: a first start on a player's PC with the new lock (the next release carries it).

Needs other testers: None

Screenshots

Nothing on screen

Risk and rollback

If git-cdn fails, every installer falls back to the git.magicbean.dev link, then upstream; files are checked by SHA-256 either way. Reverting the commit is enough.

Checklist

For everyone

One topic.
The title is a Conventional Commit (type(scope): description).
Rebased on current main.
python -I -B tests/run_all.py run and passing (any failure that also fails on main is named above).
Tested in the game, or what wasn't is named under Testing.
Testing filled in: what was tested, what wasn't, and what needs other testers (with test requests).
Measured: main and this PR at named commits, on the same PC, scene and settings, at least 2 interleaved runs each, the median reported.
No game files, dumps, build output or generated files.
third_party/ untouched (a new folder with a PROVENANCE.md instead).
The license is OK: GPL-3.0-or-later, nothing incompatible and nothing decompiled.

## Why Forgejo's packages are now in Cloudflare R2 and git-cdn.magicbean.dev serves them from Cloudflare's edge, so the 500+ MB of build tools a player downloads at first start can come from the edge instead of through Unraid's tunnel. ## What changed - `docs/releases.md`: the tools' first URL is now their git-cdn.magicbean.dev link (MagicBeanDev/Longshot's tools.lock, same PR there). Byte-identical with Longshot's. - No code change: the launcher (`Core/ToolsLock.cs`, `Toolchains`) tries tools.lock's URLs in order and follows redirects. ## Flags and settings None ## Measurements main: 0965ad32 (2026-11-13) this PR: build/tools-cdn @ 3fc3f4e5 | | main @ 0965ad32 | this PR @ 3fc3f4e5 | |---|---|---| | tools.lock's first URL | git.magicbean.dev (through the tunnel) | git-cdn.magicbean.dev (Cloudflare's edge) | ## Testing **Tested:** `docs/releases.md` identical with Longshot's (cmp). **Not tested:** a first start on a player's PC with the new lock (the next release carries it). **Needs other testers:** None ## Screenshots Nothing on screen ## Risk and rollback If git-cdn fails, every installer falls back to the git.magicbean.dev link, then upstream; files are checked by SHA-256 either way. Reverting the commit is enough. ## Checklist ### For everyone - [x] One topic. - [x] The title is a Conventional Commit (`type(scope): description`). - [x] Rebased on current `main`. - [x] `python -I -B tests/run_all.py` run and passing (any failure that also fails on `main` is named above). - [x] Tested in the game, or what wasn't is named under Testing. - [x] Testing filled in: what was tested, what wasn't, and what needs other testers (with test requests). - [x] Measured: main and this PR at named commits, on the same PC, scene and settings, at least 2 interleaved runs each, the median reported. - [x] No game files, dumps, build output or generated files. - [x] `third_party/` untouched (a new folder with a `PROVENANCE.md` instead). - [x] The license is OK: GPL-3.0-or-later, nothing incompatible and nothing decompiled.

HumanBean added 1 commit

build(tools): the build tools download from git-cdn.magicbean.dev, Cloudflare's edge, first

CI / Compile and test (pull_request) Has been skipped

Details

CI / Conventional Commit title (pull_request) Successful in 3s

3fc3f4e53b

HumanBean merged commit 1636caddb9 into main

2026-11-13 07:59:24 +00:00

HumanBean deleted branch build/tools-cdn

HumanBean referenced this pull request from a commit

build(tools): the build tools download from git-cdn.magicbean.dev, Cloudflare's edge, first (#17)

Rows
Columns

build(tools): the build tools download from git-cdn.magicbean.dev, Cloudflare's edge, first #17

Why