Harden Vercel migration releases - #158
Draft
bporterfield wants to merge 1 commit into
Draft
bporterfield wants to merge 1 commit into
bporterfield wants to merge 1 commit into
Conversation
Build before schema mutation, keep Preview databases untouched by default, and stage Production deployments behind a deep-health check before promotion. Co-Authored-By: Codex <noreply@openai.com> Signed-off-by: Ben Porterfield <benporterfield@gmail.com>
This branch has not been deployed
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.
Summary
Why
The existing vercel-build ran migrations before compilation. A broken application build
could therefore advance a shared schema even though no new application was publishable.
Preview builds also had no platform-aware default, and the manual deploy command assigned
the Production alias before checking health.
This PR is the Vercel release solution only. Hosted Fly tenant rollout is handled
independently.
The schema still must follow expand/contract: the migration completes before Vercel moves
the Production alias, so the currently live deployment must tolerate the expanded schema
during that bounded window.
Verification
Rollout verification still required
No real Vercel deployment was created from this branch. Before marking ready, exercise a
Production staging deployment against a disposable or staging database and verify build
→ migrate → staged health → promote.