Skipped monorepo deployments no longer count against Vercel limits
Vercel stopped counting deployments that it skips in monorepos against deployment rate limits. Vercel skips a project's deployment when its source code and internal dependencies have not changed, using Turborepo's package graph and lockfile analysis.
Why it matters
Monorepo teams can ship more deployments within the same plan limits, because commits that don't affect a given project no longer consume its quota.
Who should care
Teams running monorepos on Vercel, platform and DevOps engineers, agencies managing multiple client projects in one repository.
What you can do
Check Build and Deployment settings for your monorepo projects and enable skipping unaffected projects for any existing project where it is not yet on.