You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GitHub Actions: lint, typecheck, unit and integration tests on every PR
Build a multi-arch image and push to GHCR, tagged with the commit SHA —
never deploy latest
Trivy or equivalent image vulnerability scan, failing on high severity
Run the migration Job, then roll out the new image
Wait for rollout status and roll back automatically on failure
Run smoke:stack:run against the deployed environment as a post-deploy gate
Deploy to dev on merge to main; prod behind a manual approval
Notes
The rollback path is the part most pipelines skip and the part that gets asked
about. A deploy that cannot undo itself is not automated, it is just faster to break.
Automate what is currently manual.
Scope
never deploy
latestJob, then roll out the new imagesmoke:stack:runagainst the deployed environment as a post-deploy gatedevon merge to main;prodbehind a manual approvalNotes
The rollback path is the part most pipelines skip and the part that gets asked
about. A deploy that cannot undo itself is not automated, it is just faster to break.