TODO.md line 12, at v1.0.0-rc1: "pre-1.0. No git tags." The tag v1.0.0-rc1 exists on next at 2861be1 (#139), so the Status section is out of date on the one fact a reader checks first.
How to see it: git tag in a clone lists v1.0.0-rc1; TODO.md Status says there are none.
What is right: README.md says TODO.md is "where the work stands"; REPO_POLICIES.md asks that the to-do list be kept up to date "even between commits". The Status section should say which tag the tree is at and what the next tag is.
Severity: low.
Definition of done
TODO.md Status names v1.0.0-rc1 (and the branch it is on) instead of "No git tags".
The rest of Status is checked against the tree the same way.
TODO.md updated in the same commit; commit title ends (closes #N) with this issue's number.
Model: fable-5-1
`TODO.md` line 12, at `v1.0.0-rc1`: "pre-1.0. No git tags." The tag `v1.0.0-rc1` exists on `next` at `2861be1` (https://git.eeqj.de/sneak/netwatch/issues/139), so the Status section is out of date on the one fact a reader checks first.
**How to see it**: `git tag` in a clone lists `v1.0.0-rc1`; `TODO.md` Status says there are none.
**What is right**: `README.md` says `TODO.md` is "where the work stands"; `REPO_POLICIES.md` asks that the to-do list be kept up to date "even between commits". The Status section should say which tag the tree is at and what the next tag is.
**Severity**: low.
## Definition of done
- [ ] `TODO.md` Status names `v1.0.0-rc1` (and the branch it is on) instead of "No git tags".
- [ ] The rest of Status is checked against the tree the same way.
- [ ] `TODO.md` updated in the same commit; commit title ends ` (closes #N)` with this issue's number.
Model: fable-5-1
clawbot
self-assigned this 2026-10-14 16:08:48 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
TODO.mdline 12, atv1.0.0-rc1: "pre-1.0. No git tags." The tagv1.0.0-rc1exists onnextat2861be1(#139), so the Status section is out of date on the one fact a reader checks first.How to see it:
git tagin a clone listsv1.0.0-rc1;TODO.mdStatus says there are none.What is right:
README.mdsaysTODO.mdis "where the work stands";REPO_POLICIES.mdasks that the to-do list be kept up to date "even between commits". The Status section should say which tag the tree is at and what the next tag is.Severity: low.
Definition of done
TODO.mdStatus namesv1.0.0-rc1(and the branch it is on) instead of "No git tags".TODO.mdupdated in the same commit; commit title ends(closes #N)with this issue's number.Model: fable-5-1