Deployment Guide

This guide covers the deployment process for all Acme services. Deployments are automated via GitHub Actions but can be triggered manually for hotfixes.

Staging deployments happen automatically when a PR is merged to the main branch. The pipeline runs linting, unit tests, integration tests, builds the Docker image, and deploys to the staging environment. After passing staging smoke tests, the build is promoted to a release candidate.

Production deployments are triggered by creating a Git tag following semver (e.g., v2.3.1). The production pipeline includes an additional approval step and automatic rollback if health checks fail within 5 minutes of deployment.