open/ktg-plugin-marketplace
1
0
Fork 0
Code Issues Releases Activity

docs(scripts): correct the --create-tag decision date to 2026-08-10

Browse source 
Both notes dated the decision 2026-08-11. It was made on 2026-08-10, the
same evening as ac7ad42 — the date was taken from a local-time clock read
as if it were UTC (20:52 CEST is 18:52Z, still 08-10).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019i3rnU2VNRdGcrUFMnRb6R
This commit is contained in:
Kjell Tore Guttormsen 2026-08-10 20:53:13 +02:00
commit 0596e82dd9
2 changed files with 2 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

2
CLAUDE.md
View file

@ -38,7 +38,7 @@ their own Forgejo repositories under `https://git.fromaitochitta.com/open/`.
the plugin being released is *supposed* to be WARN (catalog `ref` behind `plugin.json`), so gating on the plugin being released is *supposed* to be WARN (catalog `ref` behind `plugin.json`), so gating on
WARN would brick every release. The post-write gate at the end stays — pre-flight validates the old WARN would brick every release. The post-write gate at the end stays — pre-flight validates the old
state, that one validates the new state. **`--create-tag` is deliberately NOT behind this gate** state, that one validates the new state. **`--create-tag` is deliberately NOT behind this gate**
(decided 2026-08-11): it mints and pushes the plugin tag *before* the pre-flight runs, but every (decided 2026-08-10): it mints and pushes the plugin tag *before* the pre-flight runs, but every
precondition it checks is local to that one plugin (`plugin.json` == target, badge agrees, tag precondition it checks is local to that one plugin (`plugin.json` == target, badge agrees, tag
absent), so the tag is correct by construction. A red *other* plugin can only make the tag EARLY, absent), so the tag is correct by construction. A red *other* plugin can only make the tag EARLY,
never WRONG, and the tag-absent check makes the retry idempotent — gating it would let plugin Y never WRONG, and the tag-absent check makes the retry idempotent — gating it would let plugin Y

2
scripts/release-plugin.test.mjs
View file

@ -217,7 +217,7 @@ test('a missing catalog README does not abort the ref bump', () => {
// irreversible side effect in this helper. It used to fire on the documented // irreversible side effect in this helper. It used to fire on the documented
// dry-run entry point (`<name> --create-tag`, no --write), which contradicts // dry-run entry point (`<name> --create-tag`, no --write), which contradicts
// "dry-run by default": the tag was already public before the plan was printed. // "dry-run by default": the tag was already public before the plan was printed.
// The decision (2026-08-11) was to gate it on --write and leave the catalog-wide // The decision (2026-08-10) was to gate it on --write and leave the catalog-wide
// pre-flight where it is — that gate can only prevent an EARLY tag, never a WRONG // pre-flight where it is — that gate can only prevent an EARLY tag, never a WRONG
// one, since the preconditions below already make the tag correct by construction. // one, since the preconditions below already make the tag correct by construction.