docs(genie): replace the dead v4 release recovery section - #82
Open
automagik-genie wants to merge 1 commit into
Open
automagik-genie wants to merge 1 commit into
automagik-genie wants to merge 1 commit into
Conversation
…al rules Co-Authored-By: Claude Fable 5.1 <[email protected]>
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Advanced Run ID: Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The Recovery section of
genie/_internal/runbooks/release-pipeline.mddocumented a v4-era escape hatch that no longer exists:gh workflow run sign-attest.yml --field run_id=...followed bygh workflow run release-publish.yml --field run_id=....Both workflows are
workflow_call-only today.release-publish.ymlstates it directly: "All artifacts are from one workflow run; there is no standalone dispatch or external run-id recovery path." Following the old runbook produces nothing but a confusing dispatch error during an incident.This replaces it with the rules that actually hold, verified against
version.yml,release.yml,sign-attest.ymlandrelease-publish.ymlonautomagik-dev/genie@dev:gh run rerun <run-id> --failed, but prefer re-running the whole run: the stable security gate requires every artifact's endorsement to name the same signer run, and mixing attempts fails it withverified signer run disagreement.version.ymlallocates a fresh build number and pushes commit + tag with onegit push --atomicbefore it ever callsrelease.yml, so any re-run is rejected and stops atrelease-race.next-tag-pin-skipped.detected. The remedy is landing any commit ondevthrough a normal PR; the orphan tag is already acknowledged by the Release Orphan Alert issue.version.ymlpushes the promotion tag and prints therelease.ymlinputs; a maintainer dispatches Release withchannel=stable(the only channel manual dispatch offers) and a different maintainer approves the protectedproductionenvironment.Internal page (
_internal/), so it is excluded from the public Mintlify build.🤖 Generated with Claude Code