Skipped monorepo deployments no longer count against limits
By Steven Van ·
Skipping is on by default for new monorepo projects, and existing projects can enable it under Build and Deployment in project settings.
Deployments that Vercel automatically skips in a monorepo no longer count against deployment rate limits, so teams with monorepos get more deployments from the same limits.
How skipping works
Vercel skips a project's deployment when its source code and internal dependencies haven't changed. It uses Turborepo's package graph and lockfile analysis to work out which projects a commit affects. Projects the commit doesn't touch are skipped, and those skipped deployments are no longer counted.
Availability
Skipping is enabled by default for new monorepo projects. For existing projects, it can be turned on under Build and Deployment in the project's settings.
The change is described in Vercel's limits documentation.