docs: record that merging to main promotes production - #975
Merged
Conversation
The cutover plan told the operator to prepare the website deployment without promoting it, and sequenced Task 11 around blocking forms before the hard boundary went live. Neither is possible here: threadplane promotes every main deployment automatically and main is the only branch that has ever reached production. Merging #968 promoted the boundary seconds later, ahead of the firewall block, drain, snapshot, import, and cancellation. Annotates both affected steps and states the constraint in the runbook so a future cutover either disables auto-promotion first or reconciles provider state before the code merges. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
blove
enabled auto-merge (squash)
September 3, 2026 03:34
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Contributor
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.
The growth hard-cutover plan told the operator to prepare the website deployment without promoting it, and sequenced the quiescent cutover around blocking form ingress before the hard boundary went live.
Neither is achievable on this project. The
threadplaneVercel project promotes everymaindeployment automatically, andmainis the only branch that has ever reached production across at least the last 40 production deployments. Merging #968 promoted the Neon-only boundary about five seconds later — ahead of the firewall block, the drain, the Resend snapshot, the legacy import, and the cancellation.This annotates the two affected plan steps and states the constraint plainly in the runbook, so a future cutover of this shape either disables automatic production promotion first, or is re-sequenced to reconcile the provider inventory before the code merges.
Documentation only. No source, configuration, or dependency changes.
🤖 Generated with Claude Code