Prompt·Infrastructure and environment·I02
Why production might not match main
Lists every way 'merged' can fail to mean 'live'.
Prompt
Trace a change from commit to production, including builds, migrations, deployment triggers, cache refreshes, and background services. Identify every reason production might not reflect merged code.
- What it returns
- The real pipeline as steps with their config files, and for each, how it can skip or fail without anyone noticing.
- Skip it when
- Right after the same trace, unless the release process changed.
- Changes
- Changes nothing
- Sessions
- One session
- Tools
- Automated build and Vercel config, deployment history (read-only).
- Also called
- Merge-to-production trace
Related prompts
- Database changes during a deployPromptChecks that each database change works with the old code that is still live while a release finishes.
- Dashboard and repo out of syncPromptFinds where the hosting dashboard and the repo disagree.
- Can we rebuild this database from its sources?PromptYou worry about disaster recovery, production-only state, or whether the data could be rebuilt.
More in Infrastructure and environment.