production-deployment-phase

Automate production deployments by triggering workflows that promote validated staging builds, enforce semantic version bumps, execute health checks, and apply git release tags. This ensures reliable release processes while reducing manual steps and deployment risk.

Promote staging builds to production by enforcing prerequisite-driven promotion that verifies staging validation, bumps semantic versions, tags releases, and deploys. This approach guarantees that only validated builds reach production with proper version tracking.

Health checks during production release verify deployment success by monitoring application health immediately after deployment execution. They confirm the new build is stable and operational before completing the release process and generating a ship report.

No, git tagging for releases is enforced automatically as part of the deployment workflow. The process applies semantic version bumps and creates git tags when promoting validated staging builds to production, eliminating manual tagging steps.

Yes, production deployment can be triggered using commands like /ship-prod or through automated pipelines after staging validation. This flexibility supports both manual promotion workflows and fully automated multi-environment deployment setups.

A post-deploy ship report documents the completed production deployment, including version bumps, git tags applied, health check results, and monitoring setup. It provides a comprehensive record of the release process for team visibility and auditing.