docs(scripts): correct the --create-tag decision date to 2026-08-10
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:
parent
ea8231f3c8
commit
0596e82dd9
2 changed files with 2 additions and 2 deletions
|
|
@ -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
|
||||
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**
|
||||
(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
|
||||
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
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue