ff01423f3f
The dist branch existed to carry ~120 MB payloads that could not go on main. Once payloads became release attachments it held one 500-byte manifest.json, so it was a whole branch for a reason that no longer applied. The pointer is now a release asset too: each publish recreates a one-asset release naming the versioned build. Forgejo has no /releases/latest/download/ route (404), so a pointer is still required — but keeping it in a release means nothing about distribution lives in git: no payload branch, no bot commits on main, and no push that could retrigger the pipeline (which is why writing the manifest to main was not the answer either). Recreating the tag deletes the old release AND its tag; the tag outlives its release and would otherwise block recreation. Versioned releases are retained, so older builds stay downloadable. tools/publish-dist.ps1 is removed — publishing is CI's job now. |
||
|---|---|---|
| .. | ||
| ClientVersionStoreTests.cs | ||
| LauncherSelfUpdateManagerTests.cs | ||
| LauncherSelfUpdateProcessTests.cs | ||
| LauncherUpdaterIntegrationTests.cs | ||
| LiveGiteaReleaseInstallTests.cs | ||
| ReleaseTransportTests.cs | ||
| SafeZipExtractorTests.cs | ||
| UpdateSessionBarrierTests.cs | ||
| UpdateTestSupport.cs | ||