Docs: bind emergency rollback to current main#465
Merged
Conversation
✅ Deploy Preview for luminous-fox-7c393f ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
Author
|
Post-merge verification completed on 2026-07-23.
Officer impact: the corrected instructions now bind an emergency Git rollback to exact current Officer documentation: Deployment evidence: Netlify skip attempt, provider published-deploy readback, public marker readback, main CI, and refreshed rollback preview verified. Firebase and outside providers were unchanged. |
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
1 participant
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.
Corrects the #457 rollback procedure after the post-release safety merge. The fallback must be rebased onto, and bound to, the exact current
mainimmediately before a merge—not the earlier release merge. It also records the verified unpublished Netlify safety attempt and unchanged live deploy.Refs #457
Officer impact: backup officers now have a rollback procedure that remains executable after later safety/documentation merges and explicitly stops if
mainadvances.Officer documentation:
docs/officers/PUBLISH_AND_CHECK.mdandOPERATIONS_RUNBOOK.md.Deployment evidence: documentation-only source change;
git diff --checkpasses. If merged, verify Netlify skips the ordinarymainbuild and leaves published deploy6a61c544171ea80008307623unchanged. Firebase and outside providers are unaffected.