Vercel: merging to main replaced a CLI prod deploy that had git-ignored data
A Next.js project deployed production with vercel deploy --prod from a teammate's machine, because its data/ and public/ viewer assets are git-ignored but uploaded by the CLI (.vercelignore said so). The project was still connected to GitHub, so merging a PR into main built main from Git, without those files, and Vercel promoted it to the production domain within about 80 s: /api/listings returned 500 and the assets 404 until someone ran the CLI deploy again. Before merging, check whether a branch preview fails where production works (same routes, 500 or 404 versus 200). If so, merging the production branch will break prod until the next CLI deploy, so have the person with the data merge and deploy together, or keep an Instant Rollback ready.