docs(integration): remove stale release_token path + clarify PAT-required for required-checks repos #333
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#333
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
Two stale/contradictory in
docs/integration.md:release_token stale: docs describe
secrets.release_token. Reusable workflow declares no such secret; readsRELEASE_TOOLKIT_TOKEN+GITHUB_TOKEN. Path β is unimplemented documentation.No-token path over-optimistic: docs say result is a manifest PR requiring one manual merge.
scripts/release-prep.sh:572-580says: "the rolling PR required checks never run and the PR cannot merge." Dedicated PAT is operationally NECESSARY for required-checks repos, not optional.Blocking rationale
Adopters following docs hit dead-ends. v1.0.0 adopter-facing docs must be accurate.
Fix
release_tokenreferences (or implement)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.