C.UTF-8 is a glibc built-in only from 2.35 (Debian 12+) onward; on an
older Debian runner setlocale() silently falls back to POSIX, which is
exactly the "main argv conversion failed!" crash from before. Install
locales and generate en_US.UTF-8 explicitly instead, which works on any
Debian version.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
C.UTF-8 for the win/AppImage build step: Wine's makensis was aborting
with ERR_ELECTRON_BUILDER_CANNOT_EXECUTE / "main argv conversion
failed!" under the runner's default C/POSIX locale.
Gitea rejects secret names starting with GITEA, so the registry/API
credentials are now BUILD_USER/BUILD_TOKEN.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
The registered Gitea Actions runner is a persistent Debian host labeled
docker-build, not ubuntu-latest. Debian ships no snapd by default, so
swap the PowerShell bootstrap for Microsoft's portable linux-x64
tarball, which needs only curl/tar.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Gitea Actions workflow triggered on tag push or manual dispatch: builds
the Windows NSIS/portable installers and Linux AppImage, builds+pushes
the Docker image, then creates/updates the Gitea release with a
changelog-compare link as the body and all artifacts attached. Flatpak
stays local-only (build-release.ps1) since flatpak-builder's sandbox
isn't reliable on a containerized Actions runner.
Also fixes build-release.ps1: the win.signExecutable=false override
only applied when cross-building via the WSL path, not to a genuine
native-Linux build of the "win" target (the CI's case).
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
kawaandClaude Sonnet 5