Vercel can now hold a production release until GitHub Actions pass
Deployment Checks let you gate the move from build to live production domain on named GitHub Actions workflows, closing the gap between what gets tested and what ships.
Vercel announced Deployment Checks today: you can now block a production deployment from being promoted to your live domain until selected GitHub Actions workflows finish successfully.
Until now, Vercel built a production deployment as soon as code merged and promoted it to your custom domain automatically. Deployment Checks add a step in between. In your project’s Build and Deployment settings, you pick GitHub as the check provider and choose the Actions checks to require; the deployment builds as normal but sits unpromoted until those checks pass, then Vercel aliases it to production automatically. You can still override with Force Promote from the deployment details page, and it combines with Rolling Releases for a fractional rollout afterwards. It’s available on any project connected via Vercel for GitHub.
- name: 'Notify Vercel'
uses: 'vercel/repository-dispatch/actions/status@v1'
with:
name: "Vercel - my-project: e2e-tests"Why it matters: the gap this closes is real — code tested before merge isn’t always the code that ends up released, especially once agents are merging as fast as people. This lets end-to-end tests, smoke tests or any check already running in Actions act as a release gate rather than just a merge gate, without a separate CI/CD tool.
The caveat: it relies on GitHub’s check-run naming to match workflows across runs, so renaming a job means updating the check in Vercel too, and reusing a check name across workflows can cause race conditions.