Ship a release with evidence
Create a release gate with GitHub checks, Journey Canary, and post-deploy verification.
Deployment safety is more than a passing build. A release can compile while a migration is destructive, a webhook URL has drifted, or signup is broken in the browser. The Deploy workspace turns the evidence you already have into a practical gate: inspect the change, run the important checks, verify the customer path, then watch the fragile period after promotion.
Begin at release desk
Open Deploy before a production push. Review the release verdict and the inputs it considers: connected providers, recent audits, incidents, and deployment context. This creates a single place to decide whether the release is ready, needs a waiver, or should wait for a fix.
Keep the gate calibrated to your product. A failing checkout, authentication callback, or required database migration should block promotion; a low-priority content warning should be visible without creating unnecessary release noise.
Attach GitHub evidence
Connect GitHub in Deploy → GitHub to report readiness on pushes and pull requests. The check is most valuable when it runs at the decision point—the PR—not after merge. It gives reviewers a readable verdict with the next failed condition instead of forcing them to inspect several provider dashboards.
Make a Journey Canary
Use User journeys to describe a real browser flow such as sign up, sign in, creating a project, or opening checkout. PreFlight runs the journey and preserves the result. Favor a short, money- or activation-critical path over an ambitious end-to-end test that is too fragile to trust.
For a high-risk release, run the canary on the preview or candidate environment, then repeat it in production after promotion.
Watch the release after it ships
A deploy gate only validates a moment in time. Hand the release to Health for uptime and real-user speed, and to Revenue if the change touches checkout or fulfillment. PreFlight retains the deploy and the follow-up signals together, making it easier to see whether a later incident started with this release.