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>
15 lines
711 B
Bash
15 lines
711 B
Bash
# Where Gesprächsrekorder releases are published: the one place to change.
|
|
# Sourced by build-release.sh, which writes UPDATE_JSON_URLS into
|
|
# src-tauri/tauri.conf.json (plugins.updater.endpoints), and by
|
|
# make-latest-json.sh, which points the download URLs in latest.json at
|
|
# ${RELEASE_BASE_URL}/releases/download/v<version>/<file>. See RELEASING.md.
|
|
|
|
RELEASE_BASE_URL="https://gitea.euvino.eu/public/call-recorder"
|
|
|
|
# Where the app looks for latest.json: committed to the root of master.
|
|
# Gitea 1.27.3 does not redirect releases/latest/download/<file> to a
|
|
# release's assets, so that URL is not offered here. See RELEASING.md.
|
|
UPDATE_JSON_URLS=(
|
|
"${RELEASE_BASE_URL}/raw/branch/master/latest.json"
|
|
)
|