kortix-rollback

To roll back production on Vercel and Argo CD without rebuilding, you promote a previously built Vercel artifact for the frontend and swap the Argo CD image tag for the backend. This reverts both surfaces to a prior stable version using prebuilt artifacts.

The safest way to revert a broken production release during incident response is to use prebuilt artifacts for rollback while running a database migration drift check. This validates schema compatibility before reversion to prevent data corruption.

To handle database migration drift when rolling back, you must run a pre-rollback validation check. This ensures that database migrations between your current version and the target older version are additive and safe for the older codebase.

Yes, you can skip the frontend rebuild when rolling back backend-only changes in Argo CD. The rollback process automatically skips frontend Vercel build promotions for backend-only changes to prevent clobbering the existing stable frontend.

Vercel build promotion supports coordinated rollbacks with Argo CD image tag swaps by targeting any previously released version. It reverts both frontend and backend surfaces simultaneously using prebuilt artifacts with zero rebuild steps.

You should not use a GitOps rollback approach for production incidents when database migrations between your current and target versions are not additive. Non-additive schema changes require forward-fixing instead of reverting to avoid data corruption.