From 611336bb330c6cd9f46e16a80ad8431053612e26 Mon Sep 17 00:00:00 2001 From: Lilleman auf Larv Date: Fri, 4 Sep 2026 11:20:29 +0200 Subject: [PATCH] Name the tag-push permission and the one-commit bump in the release checklist --- todo.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/todo.md b/todo.md index 8c5559a..aa9b9ef 100644 --- a/todo.md +++ b/todo.md @@ -113,8 +113,11 @@ The numbering is the order the work was planned in, not the order it ships. guard. §11's scanning rule is the whole argument; the pipeline persona feeds documents nobody typed. - [ ] **5 — Ship `0.1.0`.** Only the maintainer's own acts are left (§15): make the Gitea repo - public (§6), create the `NPM_TOKEN` secret, and open the bump PR that sets `version` to - `0.1.0` and drops `private: true`, the guard against any earlier publish. `0.1.0` is the + public (§6), create the `NPM_TOKEN` secret, confirm the Actions token may push tags — the + publish succeeds and the tag push then reddens the run, though the next push to `main` + retries the tag alone — and open the bump PR that sets `version` to `0.1.0` and drops + `private: true`, the guard against any earlier publish. The bump and the drop go in one + commit: dropping `private` alone publishes `0.0.0`, which also differs from npm's nothing. `0.1.0` is the markdown round-trip: both markdown directions, the types, `isAdfDocument`, proved over the checked-in corpus. **Settled** (the maintainer, 2026-09-01): the round-trip proved over the checked-in corpus