Repository navigation
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
ripgrim
force-pushed
the
codex/vercel-staging
branch
from
October 23, 2026 04:41
1c9440f to
b7c19dc
Compare
ripgrim
force-pushed
the
codex/vercel-staging
branch
from
October 23, 2026 04:50
b7c19dc to
9faa2d6
Compare
This branch was successfully 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
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
Apply database migrations during Vercel staging builds.
Problem
The staging environment uses an isolated Neon database. The API build skips migrations outside production, so staging can run outdated schemas.
Solution
Run migrations for production and staging deployments. Keep other previews migration-free. Document the main-to-staging and release-to-production flow.