Vercel announced on October 21, 2026, that automatically skipped deployments for unaffected monorepo projects no longer count toward deployment rate limits. The change was available immediately; automatic skipping defaults on for new monorepo projects and can be enabled for existing projects. StackGrade also reported the change, citing Vercel’s announcement. Sources: Vercel, StackGrade
Vercel’s documentation requires GitHub-connected repositories using npm, Yarn, pnpm or Bun workspaces. Package names must be unique, and internal dependencies must be explicitly declared. Each app needs its own Vercel project and Root Directory setting. Vercel says it uses Turborepo’s package graph and lockfile analysis to identify affected projects. Sources: Vercel
According to Vercel’s documentation, source changes, internal dependency changes and relevant lockfile changes mark a project as affected. Changes outside workspace definitions trigger every application. Automatic skips also avoid concurrent build slots. Ignored Build Step cancellations still count toward deployment and concurrent-build limits. Sources: Vercel
In an illustrative example, a commit affects one of ten eligible projects. If Vercel automatically skips the unaffected projects, that produces one counted deployment and nine exempt skips. Disabling automatic skipping or using Ignored Build Step cancellations forfeits that accounting benefit. Sources: Vercel
What to do
- For pnpm workspaces, define the app and shared-package paths in the root pnpm-workspace.yaml, for example with packages: ['apps/*', 'packages/*'].
- Give each app its own Vercel project and set Root Directory to the app’s directory.
- Use unique package names and declare shared-package dependencies in each consuming app’s package.json.
- Commit the root lockfile so Vercel can detect changes affecting project dependencies.
- For an existing project, enable Settings > Build and Deployment > Root Directory > Skip deployment, then save. Sources: Vercel