Skip to content

Automatic certified revert of red release d8dc028ba - #168

Merged
github-actions[bot] merged 2 commits into
mainfrom
ship/revert-d8dc028ba
Aug 31, 2026
Merged

Automatic certified revert of red release d8dc028ba#168
github-actions[bot] merged 2 commits into
mainfrom
ship/revert-d8dc028ba

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

The release gate failed for d8dc028. This revert is certified, merged and re-gated by the SAME run that detected the failure. No human is required.

@github-actions
github-actions Bot enabled auto-merge (squash) August 31, 2026 19:20
@github-actions
github-actions Bot merged commit b40d060 into main Aug 31, 2026
15 checks passed
github-actions Bot added a commit that referenced this pull request Aug 31, 2026
…ECOVERY_TOKEN (#170)

A GITHUB_TOKEN push cannot trigger the push-event ci runs that branch
protection recognises, so bot-created ship/revert-* branches left every
required context stuck at 'Expected' even after a green dispatched ci run
(observed live on PR #168; unblocked manually with a user-authenticated
empty commit). When the SHIP_RECOVERY_TOKEN secret (fine-grained PAT,
this repo, Contents + Workflows read/write) is configured, the recovery
path now pushes the revert branch with it — a user event, so ci starts
on push and reports the required contexts exactly like a normal ship
branch — and waits on that push-event run. Without the secret the old
dispatch path is unchanged, and a stalled recovery merge now files an
issue carrying the exact manual unblock and the permanent fix.



Claude-Session: https://claude.ai/code/session_01VkMDoMT8yVLvkhSJ6eritu

Co-authored-by: AgentTanuki <AgentTanuki@users.noreply.github.com>
Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant