From 5be7206a932addcb5cee0b1bba10113022ce2754 Mon Sep 17 00:00:00 2001 From: Daniel Maksymilian Syrnicki Date: Mon, 13 Apr 2026 20:28:08 +0200 Subject: [PATCH] docs: add runner setup + release publish to roadmap as next actions Mark release-process + CI work complete. Add two next-session TODOs for Daniel: stand up the forgejo-runner (without which CI queues forever) and publish the 26.0-alpha Forgejo Release. Co-Authored-By: Claude Opus 4.6 (1M context) --- README.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/README.md b/README.md index e6c3dfb..9d56206 100644 --- a/README.md +++ b/README.md @@ -103,6 +103,9 @@ None of these nail the "your dad can set this up" experience. The installer wiza - [x] Arch running on Proxmox, custom image builds in progress (Robert) - [x] Competitor analysis — see [docs/competitors.md](docs/competitors.md) - [x] Wizard flow spec — see [docs/wizard-flow.md](docs/wizard-flow.md) +- [x] Release process + CI — CalVer tags, conventional commits, Forgejo Actions (ruff, pytest, JSON, link checks), `26.0-alpha` tagged +- [ ] **Stand up Forgejo runner** — see [docs/runner-setup.md](docs/runner-setup.md) *(Daniel, next session — without this CI queues forever)* +- [ ] **Publish `26.0-alpha` Forgejo Release** — [releases/new](https://forgejo.sourcegate.online/daniel/homebase/releases/new), paste CHANGELOG section, tick Pre-release *(Daniel, next session)* - [ ] **Base OS bootable image** — Robert gets a minimal Arch image that boots, runs Docker, serves the installer webapp at `https://proksi.local` *(next blocker)* - [ ] Installer wizard screens S5–S8 (domain, SSL, diagnostic, confirm) - [ ] Caddy + Authentik wired into first-boot bootstrap