In short
- Deployments skipped automatically in a monorepo no longer count toward deployment limits.
- New projects have skipping on; for older ones you enable it in settings.
In short: if you keep several apps in one repository, Vercel no longer counts the deployments it skipped itself against your limits.
What changed
- Vercel skips a project’s deployment when neither its code nor its internal dependencies changed.
- To decide which projects a change affects, it uses Turborepo’s package graph and lockfile analysis.
- Those skipped deployments no longer count toward deployment rate limits.
How to switch it on
New monorepo projects have skipping on by default. For existing ones, enable it in project settings: Build and Deployment, Root Directory section, the Skip deployment switch. The docs list requirements: a GitHub repository, npm, yarn, pnpm or Bun workspaces, unique package names and explicitly declared dependencies between them.
How to read this
The post does not give the actual limit values or which plans are affected, so check Vercel’s limits documentation. The change helps only where skipping works, meaning the requirements are met. I cover related tools in the app builders hub.