chore #14740: drop appimage and the unsupported feed url

Verified on Gitea 1.27.3: releases/latest/download/<file> does not
redirect to a release's assets (404), so that update-feed endpoint is
dead. Only raw/branch/master/latest.json works; keep that one in
release.env and tauri.conf.json and document it as the mandatory feed
in RELEASING.md.

Also drop the AppImage (user: it is huge and we don't need it): bundle
targets become nsis+deb, build-release.sh only builds the .deb on
Linux, and make-latest-json.sh no longer writes a Linux platform entry
at all (Debian builds don't self-update).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This commit is contained in:
hauke
2026-11-06 12:29:53 +01:00
co-authored by Claude Sonnet 5
parent 572c685396
commit eff07d2f59
5 changed files with 43 additions and 73 deletions
+35 -52
View File
@@ -3,7 +3,7 @@
A release consists of:
- the Windows NSIS installer (per-user, no admin rights), cross-built on Debian,
- the Debian `.deb` and `.AppImage`,
- the Debian `.deb`,
- an updater signature (`.sig`) for each of them,
- `latest.json`, the update feed the installed Windows apps read.
@@ -46,8 +46,7 @@ restarts the app. Debian builds do not update themselves.
`https://gitea.euvino.eu/public/call-recorder`. The download URLs in `latest.json`
point to `${RELEASE_BASE_URL}/releases/download/v<version>/<file>`.
- `UPDATE_JSON_URLS`: where the app looks for `latest.json`. `build-release.sh`
writes them, in this order, into `plugins.updater.endpoints` in
`src-tauri/tauri.conf.json`.
writes them into `plugins.updater.endpoints` in `src-tauri/tauri.conf.json`.
Do not edit the endpoints in `tauri.conf.json` by hand. Change `release.env`; the
next release build writes them into `tauri.conf.json`.
@@ -55,43 +54,25 @@ next release build writes them into `tauri.conf.json`.
The repository and its releases must be readable without logging in: the app
downloads anonymously.
### The two feed URLs
### The feed URL
The app tries the endpoints in order and uses the first one that returns a release.
A `404` or a network error on one moves on to the next one:
Verified on Gitea 1.27.3: `releases/latest/download/<file>` does **not** redirect
to a release's assets, even for the newest non-draft, non-prerelease release —
requesting it returns `404`. So the feed lives only at
1. `https://gitea.euvino.eu/public/call-recorder/releases/latest/download/latest.json`:
`latest.json` as an asset of the newest release (not a draft, not a pre-release).
This works only if Gitea redirects `releases/latest/download/<file>` to the newest
release.
2. `https://gitea.euvino.eu/public/call-recorder/raw/branch/master/latest.json`:
`latest.json` committed to the root of `master`.
Each release serves both:
- uploading the release assets covers URL 1 (step 7 below);
- committing `latest.json` to the root of `master` covers URL 2 (step 8 below).
The endpoints are compiled into the app. Installed versions keep asking the URLs
they were built with, which is why both are configured from the start.
After the first release, check which URL works:
```sh
curl -sIL https://gitea.euvino.eu/public/call-recorder/releases/latest/download/latest.json
curl -sIL https://gitea.euvino.eu/public/call-recorder/raw/branch/master/latest.json
```
https://gitea.euvino.eu/public/call-recorder/raw/branch/master/latest.json
```
The final status of a working URL is `200`. Then:
`latest.json` committed to the root of `master`. This makes committing
`latest.json` after every release **mandatory**, not optional (step 8 below) —
there is no redirect to fall back on.
- **URL 1 works:** a later version may drop URL 2 from `UPDATE_JSON_URLS`. Every
installed version also asks URL 1, so step 8 is no longer needed.
- **Only URL 2 works:** a later version may drop URL 1. Step 8 (committing
`latest.json`) stays part of every release.
Caveat: if URL 1 answered `200` with something that is not JSON (e.g. an HTML page),
the updater would stop there instead of trying URL 2. Gitea answers a missing file
with `404`, which falls through as intended.
Versions 0.1.0 and 0.1.1 were built with both URLs compiled in (the endpoints
are fixed at build time; installed apps keep asking the URLs they were built
with). They still try `releases/latest/download/latest.json` first on every
check; that is harmless — it 404s and the app falls through to the
`raw/branch/master` URL, which answers normally.
## Releasing a version
@@ -120,8 +101,8 @@ e.g. for the first release `0.1.0`.
- sets the version in `src-tauri/tauri.conf.json`, `src-tauri/Cargo.toml` and
`ui/package.json` (the build updates `Cargo.lock` too), and writes the endpoints
from `release.env` into `tauri.conf.json`,
- builds the Windows installer (`scripts/build-windows.sh`), the `.deb` and the
`.AppImage`, each with its `.sig`,
- builds the Windows installer (`scripts/build-windows.sh`) and the `.deb`, each
with its `.sig`,
- copies them to `dist-release/0.1.1/` under ASCII names (`Gespraechsrekorder_…`)
and writes `latest.json` with `scripts/make-latest-json.sh`.
@@ -130,12 +111,11 @@ e.g. for the first release `0.1.0`.
3. Check `dist-release/0.1.1/`. It should contain:
| File | Purpose |
| File | Purpose |
|------------------------------------------------------|--------------------------------------|
| `Gespraechsrekorder_0.1.1_x64-setup.exe` (+ `.sig`) | Windows installer and update package |
| `Gespraechsrekorder_0.1.1_amd64.deb` (+ `.sig`) | Debian package |
| `Gespraechsrekorder_0.1.1_amd64.AppImage` (+ `.sig`) | Debian AppImage |
| `latest.json` | Update feed |
| `Gespraechsrekorder_0.1.1_x64-setup.exe` (+ `.sig`) | Windows installer and update package |
| `Gespraechsrekorder_0.1.1_amd64.deb` (+ `.sig`) | Debian package |
| `latest.json` | Update feed |
4. Commit the version bump the script left in the working tree:
@@ -155,12 +135,14 @@ e.g. for the first release `0.1.0`.
<https://gitea.euvino.eu/public/call-recorder/releases/new>. Do not mark it as a
draft or a pre-release, otherwise it is not the "latest" release.
7. Upload every file from `dist-release/0.1.1/` as a release asset, keeping the file
names (`latest.json` points to them). Upload the installers, packages and `.sig`
files first and **`latest.json` last**. As soon as `latest.json` is visible,
installed apps may try to download the files it lists.
7. Upload the installer, the `.deb` and their `.sig` files from
`dist-release/0.1.1/` as release assets, keeping the file names (`latest.json`
points to them). `latest.json` itself does not need to be uploaded as a release
asset: the feed is served from the committed file (step 8), not from
`releases/latest/download/latest.json` (see "The feed URL" above).
8. Only after all assets are uploaded, publish the feed for URL 2 as well:
8. Only after all assets from step 7 are uploaded and downloadable (their URLs are
what the feed will point to), commit the feed:
```sh
cp dist-release/0.1.1/latest.json latest.json
@@ -169,15 +151,16 @@ e.g. for the first release `0.1.0`.
git push origin master
```
Committing `latest.json` is mandatory for every release — it is the only
place the feed lives.
9. Check the feed:
```sh
curl -sL https://gitea.euvino.eu/public/call-recorder/releases/latest/download/latest.json | jq .
curl -sL https://gitea.euvino.eu/public/call-recorder/raw/branch/master/latest.json | jq .
```
The URL(s) that work must show the new version, and the `url` entries must
download.
It must show the new version, and the `url` entry must download.
## Checking an update on Windows 11
@@ -211,5 +194,5 @@ and 30 minutes, then every 6 hours. The log
- `RELEASE_ALLOW_KEY_MISMATCH=1` lets `build-release.sh` build with a key that does
not match `plugins.updater.pubkey`. Use it only to test the pipeline with a throwaway
key. Installed apps reject such a release, so never publish it.
- `latest.json` also lists the AppImage (`linux-x86_64`). The Debian builds do not
check for updates yet.
- `latest.json` only lists `windows-x86_64`. Debian installs from the `.deb` and
does not self-update, so Linux has no entry in the feed.