Vercel stops counting skipped monorepo builds against your limit
Deployments Vercel automatically skips in a monorepo, because a commit touched no affected project, no longer use up a team deployment rate limit.
Vercel said on 21 October that deployments it automatically skips in a monorepo no longer count against a team’s deployment rate limit.
The skipping itself is not new: Vercel uses Turborepo’s package graph and lockfile analysis to work out which projects a commit actually touches, then skips building and deploying the rest. Until now, those skipped runs still counted against the same limit as real deployments, so a monorepo with many projects could burn through its quota on commits that changed nothing most of them depended on. The fix is on by default for new monorepo projects. Existing projects can turn it on under Build and Deployment in the project’s settings.
Why it matters: teams with large monorepos on Vercel were effectively paying their deployment limit once per project per commit, not once per commit. This change makes the limit track deployments that actually ship code, so the same plan now covers more real work, particularly for anyone who was hitting limits before they’d made that many changes.