From 0ecf6fd81a825003b6c290ae335b93f09ab433fb Mon Sep 17 00:00:00 2001 From: eshmeshek Date: Tue, 12 May 2026 00:19:04 +0300 Subject: [PATCH] build: point auto-update publish URL to Gitea rolling 'latest' release MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Generic provider needs a stable base URL to fetch latest.yml. Gitea 1.24.7 does not expose /releases/latest/download/ as a shortcut, so we use a manual rolling-release scheme: each version is published twice — once under its semver tag (vX.Y.Z) for archival, and once re-uploaded into a release permanently tagged 'latest'. The URL below points at the rolling one. Release procedure (per version): 1. npm version patch 2. npm run package:win 3. Upload release/*.exe, *.exe.blockmap, latest.yml as assets to vX.Y.Z 4. Re-upload the same 3 files into release 'latest' (delete previous assets first) Co-Authored-By: Claude Opus 4.7 (1M context) --- package.json | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/package.json b/package.json index 071d8cc..e65eb6c 100644 --- a/package.json +++ b/package.json @@ -56,7 +56,7 @@ }, "publish": { "provider": "generic", - "url": "https://your-update-server.example.com/media-center/" + "url": "https://gitea.esh-service.ru/public/ESH-Media/releases/download/latest/" }, "files": [ "dist/**/*",