The installer is unsigned, so latest.yml is now signed with an Ed25519 key and the
app verifies the downloaded installer against it before installing.
npm run release -- patch|minor bumps, gates, tags, builds, signs, publishes,
re-verifies the public feed and pushes; --resume continues after a failure.
The retired GitLab registry publisher is removed.
- desktop: mock @nut-tree-fork/nut-js in the shared Vitest setup; template
tests reached the real TextInsertService and libnut killed the worker on the
display-less Linux runner ("Could not open main display").
- mobile: the knowledge realtime test now unsubscribes, so the deletion
reconcile interval no longer keeps Jest alive forever.
- set-forgejo-secrets.mjs syncs every Forgejo secret from the root .env and
refuses local URLs; SUPABASE_URL had been registered as 127.0.0.1:55321, so
payple-renew never succeeded.
Two tagged release pipelines failed and no installer has been published since
1.1.0. The cause is not in the build: the release repository has no Actions
secrets at all, so every run stops at the signing guard.
A helper now reports which release secrets are missing and registers them once
the signing material exists, and the release guide documents the required
values, the Forgejo-side check, and how to re-run a pipeline for an existing
tag without recreating it.