From 8d42b94c6c631b00b8eed8ea3238f298da87139e Mon Sep 17 00:00:00 2001 From: clawbot <35+clawbot@noreply.example.org> Date: Mon, 19 Oct 2026 05:51:30 +0000 Subject: [PATCH] TODO.md Status says where release candidates are tagged (closes #157) Status said there were no git tags, but one is tagged on `next`. It now says release candidates are tagged on `next`, names the first one, and gives the command that lists them, so it stays true as more are tagged. The other Status sentences match the tree and are unchanged. Model: opus-5-5 --- TODO.md | 15 ++++++++++----- 1 file changed, 10 insertions(+), 5 deletions(-) diff --git a/TODO.md b/TODO.md index 27b791b..ee97939 100644 --- a/TODO.md +++ b/TODO.md @@ -9,11 +9,12 @@ # Status -pre-1.0. No git tags. `main` is the stable branch and `next` the development -branch, which every PR targets. The frontend and the Go backend ship as one -Docker image, and the Gitea workflow `.gitea/workflows/check.yml` runs -`script/cibuild` on every push, and cancels the older run on the same branch. -Working toward 1.0.0. +pre-1.0. Release candidates are tagged on `next`, the first being `v1.0.0-rc1`; +`git tag --merged origin/next` lists them. `main` is the stable branch and +`next` the development branch, which every PR targets. The frontend and the Go +backend ship as one Docker image, and the Gitea workflow +`.gitea/workflows/check.yml` runs `script/cibuild` on every push, and cancels +the older run on the same branch. Working toward 1.0.0. # Next Step @@ -22,6 +23,10 @@ Run `make frontend-viewport-test` in CI as its own step; it is not part of # Completed Steps +- 2026-10-19: Status names `v1.0.0-rc1`, the first release candidate, and says + release candidates are tagged on `next`, where it said there were no git tags + ([#157](https://git.eeqj.de/sneak/netwatch/issues/157)). The rest of Status + matches the tree - 2026-10-19: `netwatch-server` starts the server only when given no arguments ([#179](https://git.eeqj.de/sneak/netwatch/issues/179)). `check-cidr CIDR` and `prepare-data-dir DATA_DIR` behave as before; any other arguments, such as a -- 2.54.0