Deploy
Production releases
Build, validate, promote, observe, and roll back Production deployments without confusing Ready with Current.
A Production release is the workflow that moves validated application output onto your production domains. Creating a Production deployment is not the same as serving Production traffic.
Release flow
- Build with Production configuration. A Production deployment uses Production environment variables and settings. See Environments.
- Reach Ready. A successful build becomes Ready. Ready means the artifact can be assigned; it does not mean it is Current.
- Understand Staged vs Current. When auto-assign is off, a Ready Production deployment stays Staged until you promote it. The Current deployment is the one serving production domains.
- Validate the immutable deployment URL. Open the deployment URL and check critical paths before promotion. See Deployment URLs.
- Promote to production domains. Instant promote reuses the Ready artifact with no rebuild. See Promoting deployments.
- Observe the release. Confirm requests, errors, and cache behavior in Observability.
- Roll back without rebuilding. Instant rollback points production domains at a previous Ready Production deployment. See Rolling back deployments.
Automatic assignment
When Auto-assign production domains is on (the default), a new Ready Production deployment becomes Current after build. If the build fails, production traffic stays on the existing Current deployment.