RecompLauncher can only install from GitHub releases: ask its makers for Forgejo or manifest-URL support #74

New issue

Open

opened 2026-11-13 01:48:32 +00:00 by HumanBean · 0 comments

HumanBean commented

2026-11-13 01:48:32 +00:00

Owner

Why

RecompLauncher (source) installs and updates a recomp from its releases, but it only finds releases on GitHub: its guide says it "installs and updates your recomp straight from your GitHub releases", and recomplauncher.json's repo is a GitHub owner/name with no field for another forge, a base URL or a download URL. Longshot releases on git.magicbean.dev (Forgejo), so RecompLauncher can't find Longshot by itself. Today a player has to download the Windows zip or the AppImage and add it to RecompLauncher by hand as a local build.

What we want

Support in RecompLauncher for releases that aren't on GitHub. Either:

A Forgejo/Gitea source: e.g. "forge": "https://git.magicbean.dev" next to "repo": "MagicBeanDev/Longshot". Forgejo's releases API is nearly GitHub's (GET /api/v1/repos/{owner}/{repo}/releases, releases/latest, assets with browser_download_url), so it should mostly be a different base URL and the /api/v1 prefix; or
A plain manifest URL: a field naming a JSON file (or the release list) at any URL, so any host works.

Steps

Ask RecompLauncher's makers (an issue on github.com/elripalda/RecompLauncher, or their contact), proposing option 1 or 2 with the API details above. Link it here.
When it lands: set the new field in recomplauncher.json (it ships in the Windows zip and the AppImage), test install and update from RecompLauncher on Windows and Linux, and update docs/releases.md's RecompLauncher section.
Until then: docs/releases.md says RecompLauncher needs a hand-added local build, and the LongshotLauncher is the supported way to install.

Not doing (unless asked)

A GitHub mirror of Longshot's releases just for RecompLauncher: it needs a GitHub owner and token, and copies every release to a second host.

See #13 (the release process) and MagicBeanDev/LongshotLauncher.

## Why [RecompLauncher](https://recomplauncher.com) ([source](https://github.com/elripalda/RecompLauncher)) installs and updates a recomp from its releases, but it only finds releases on **GitHub**: its guide says it "installs and updates your recomp straight from your GitHub releases", and `recomplauncher.json`'s `repo` is a GitHub `owner/name` with no field for another forge, a base URL or a download URL. Longshot releases on git.magicbean.dev (Forgejo), so RecompLauncher can't find Longshot by itself. Today a player has to download the Windows zip or the AppImage and add it to RecompLauncher by hand as a local build. ## What we want Support in RecompLauncher for releases that aren't on GitHub. Either: 1. **A Forgejo/Gitea source**: e.g. `"forge": "https://git.magicbean.dev"` next to `"repo": "MagicBeanDev/Longshot"`. Forgejo's releases API is nearly GitHub's (`GET /api/v1/repos/{owner}/{repo}/releases`, `releases/latest`, assets with `browser_download_url`), so it should mostly be a different base URL and the `/api/v1` prefix; or 2. **A plain manifest URL**: a field naming a JSON file (or the release list) at any URL, so any host works. ## Steps - [ ] Ask RecompLauncher's makers (an issue on github.com/elripalda/RecompLauncher, or their contact), proposing option 1 or 2 with the API details above. Link it here. - [ ] When it lands: set the new field in `recomplauncher.json` (it ships in the Windows zip and the AppImage), test install and update from RecompLauncher on Windows and Linux, and update `docs/releases.md`'s RecompLauncher section. - [ ] Until then: `docs/releases.md` says RecompLauncher needs a hand-added local build, and the LongshotLauncher is the supported way to install. ## Not doing (unless asked) A GitHub mirror of Longshot's releases just for RecompLauncher: it needs a GitHub owner and token, and copies every release to a second host. See #13 (the release process) and MagicBeanDev/LongshotLauncher.

HumanBean added the

enhancement

label

2026-11-13 01:48:39 +00:00