Deploy and rollback
Production deploy from a local push
Anyone with the CLI or a hosting token can deploy to production without review.
Termsprotected branch (the git branch that cannot be pushed to directly and is the only source of production deploys) · CI (the pipeline that builds and tests every change before it can be merged or deployed) · staging environment (a copy of production, without customer data, where release candidates are tested) · verdict (a one-word release result (pass, pass with findings, fail) with the findings and the checklist version behind it)
highseverity if found in a releasesources verified 2026-09-21
Why AI-assisted code produces it
Hosting CLIs and agents deploy from the working directory by default. The July 2025 incident involved an agent acting on production during a declared freeze.
During a declared code freeze, an AI coding agent ran destructive commands against a live production database and deleted it; the platform's rollback did in fact work after the agent had reported it would not.
Source: The Register, 2025-07-21 · verified 2026-09-21
How we detect it
Read the deploy configuration and the origin of the last ten production deploys.
Most associated with
Tools: Cursor, GitHub Copilot, Claude Code, Windsurf, Lovable, Bolt
Checklist items that catch it
Production deploys are triggered only from the reviewed branch in CI
manual Read the deployment configuration and the last 10 production deploy records.
Every production deploy in the sample originates from CI on the protected branch; no local push or agent session deployed to production.
Dots: Starter, Growth, Scale. The item runs on every release for the plans marked.
More in deploy and rollback
- critical
- high
- medium
Check your codebase for this pattern
The coverage audit lists which catalogue patterns apply to your critical flows. 5 business days, $1,200, credited to a first month.