docs(readme): reconcile publish_mode:immediate default vs 'human-gated every release' claim #332
Labels
No labels
bump
major
bump
minor
bump
patch
kind/bug
kind/chore
kind/docs
kind/feature
priority/critical
priority/high
priority/low
priority/medium
size/L
size/M
size/S
size/XL
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
frankenbit/release-toolkit#332
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Finding
README claims: "Gates every release behind a human. ... you click Publish"
Quick-start example + reusable workflow default to
publish_mode: immediate. Under default, merging prep PR publishes release directly — no Publish click.Blocking rationale
Advertising safety property that doesn't hold by default is v1.0.0 blocker. Adopters may select tool specifically for the extra gate.
Fix
Option A (recommended): change default to
publish_mode: draft.Option B: rewrite README to accurately describe current default + how to enable draft mode.
Option C: default draft in reusable, keep immediate in quick-start with tradeoff note.
Anchor
External correctness cold-read (anonymous ChatGPT session, uploaded to operator 2026-07-03). Full review surfaced 10 findings across 5 blocking-v1.0.0 + 2 should-fix pre-v1.0.0 + 3 post-v1.0.0 backlog. This tracker addresses one of them.
BLOCKING v1.0.0.
immediate— #332 took Option A and Option B was correct #827