4 Commits

Include renames

Author	SHA1	Message	Date
kawa	00bd5d8b13	Now build everything under WSL (so I can work with unsigned exe's on my work computer :P )	2026-08-14 13:20:30 +02:00
kawa	cc439c1152	Modified publish pipeline for WSL (flatpak, appimage builds)	2026-08-13 15:13:42 +02:00
kawa	3ed8f5683f	Fixed publish script+added options to separate binaries publishing. ... Bumped package.json to 2.0.0	2026-08-13 08:48:34 +02:00
kawaandClaude Opus 5	f2b9f28d14	build: add Gitea release scripts and npm entry points ... scripts/build-release.ps1 packages the desktop installers; scripts/publish.ps1 pushes the container image to git.azuze.fr and attaches the installers to the Gitea release for the same tag. The split keeps a local build free of any credential, and lets a failed upload be retried with -BinariesOnly -NoBinaryBuild without paying for the build again. Two details the plain `npm run dist:*` path gets wrong for a release: - package.json's global artifactName resolves NSIS and portable to the same file name, so one silently overwrites the other. The build script passes distinct -c.nsis.artifactName / -c.portable.artifactName. - Artifact names now carry the tag, so publish.ps1 can glob exactly one tag's files and never ship a stale one. electron-builder's update metadata (.blockmap, latest*.yml, the NSIS .7z payload) is swept out of dist/ so it cannot match that glob and end up attached to the release. The tag defaults to v<package.json version> rather than git describe, because electron-builder stamps package.json into the app: a SHA-based tag would name an installer whose About box disagrees with it. Also brings scripts/server.cjs, vendor.mjs and make-icon.cjs under version control, which the release scripts and the Docker build both call. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-12 12:56:11 +02:00