a85ab799a3
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. |
||
|---|---|---|
| .. | ||
| deployment | ||
| design | ||
| design-refs | ||
| map | ||
| phases | ||
| re-findings | ||
| tdd-red | ||
| v2 | ||
| v3 | ||
| monetization-plan.md | ||
| REFACTOR_POLICY.md | ||
| REFACTOR_WAVE1_REPORT.md | ||
| REFACTOR_WAVE2_REPORT.md | ||