|
Some checks failed
deploy-site / deploy (push) Failing after 31s
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. |
||
|---|---|---|
| .. | ||
| 00-index.md | ||
| 01-system-overview.md | ||
| 02-infrastructure.md | ||
| 03-shared-packages.md | ||
| 04-desktop-app.md | ||
| 05-web-app.md | ||
| 06-mobile-app.md | ||
| 07-api-server.md | ||
| 08-admin-console.md | ||
| 09-supabase-backend.md | ||
| 10-feature-catalog.md | ||
| 11-gap-backlog.md | ||
| 12-update-protocol.md | ||