Vibe Coder · Unit 15: Deploy on Vercel · Lesson 7 of 7

Build settings and CI

Engineers: make deployment depend on passing checks, separate environments, and run migrations as part of the release.

Read the short notes and pictures.Do everything inside a blue frame.

Reliable releases

Vercel deploys on every push. Making that safe means putting your checks in front of the merge, giving each environment its own configuration and data, and making schema changes part of the pipeline.

A 3D scene of coloured blocks and cards. The gate: pull request, CI passes, merge and deploy.
Merges, and so deploys, require CI to pass.

What to set up

Required checks

Type-check, lint, tests and build must pass to merge.

Environment separation

Separate keys and, ideally, a separate database for preview.

Migrations in the pipeline

Applied automatically, before or with the deploy.

Rollback

Know how to promote the previous deployment.

A 3D scene of coloured blocks and cards. Three environments: development, preview, production.
Development, preview and production stay separate.

Release hygiene

  1. Small pull requests

    Easier to review and to revert.

  2. A smoke test after deploy

    An automated check of the main path on production.

  3. Alerts

    On error rates and failed deploys.

ActivityBuild stepYour app, live

Harden your release process

Make CI a required check, separate preview and production configuration, run migrations in the pipeline, and add a post-deploy smoke test. Practise a rollback once.

Done when

Your release process is repeatable.

Keep these

  • Gate deploys on CI.
  • Separate environments.
  • Automate migrations and practise rollback.