Vercel - CI - TypeScript - Deployments
3 min lectura

Vercel is retiring native lint and typecheck checks on Nov 30: a migration checklist

Identify affected native Deployment Checks and move lint and type checking to CI or the Build Command while preserving failure gates.

Vercel is retiring native lint and typecheck checks on Nov 30: a migration checklist

A project can keep deploying after it quietly loses a check that used to stop code with lint or type errors. On November 17, 2026, Vercel announced that its native Lint and Typecheck Deployment Checks will be removed on November 30. New checks of those types can no longer be added; existing ones run until the deadline. If a native check blocks production for you, move the command and prove that failures still block the relevant step.

Find out whether your project is affected

Open your project's Build and Deployment settings and look for Lint or Typecheck entries with Vercel as provider. Those are the affected native checks. Vercel says other Deployment Checks and commands already running in GitHub Actions or your Build Command are unaffected. Inventory your projects before changing CI; the announcement does not mean that every Vercel deployment loses type checking.

For each affected project, note the actual package.json script, where it runs, and whether the check is required before a production release. Simply moving a command into a workflow that reports a result but never blocks a merge or promotion is not an equivalent replacement.

Migrate the safety gate

  1. Run the exact scripts locally from a clean checkout. Fix pre-existing failures before changing the mechanism.
  2. Choose an execution path. Vercel recommends Vercel CI or your own CI. If your team already uses GitHub Actions, adding lint and type checking to that workflow and requiring the check may be the shorter path.
  3. Test failure behavior. On a safe branch, introduce a deliberate type error, run the workflow, and confirm that it prevents the action your former check prevented. Revert it and verify the passing state.
  4. Remove the old check only after the new gate works. Document where people see the result and who can bypass it.
Four-step diagram for migrating and testing lint and type checks
Test the failure gate, not just that CI runs.

Another option is to run npm run lint && npm run typecheck && npm run build in the Build Command when those scripts exist. Vercel warns that this can increase build time, and a failing command fails the build. Adapt the pattern to your package manager and scripts; it is not a universal command to paste into every project.

Vercel CI availability matters

Vercel CI is in public beta. Its current requirements include a Turborepo task graph, Turborepo 2.11.7 or later, and Vercel CLI 64.3.1 or later. The beta supports private GitHub repositories; public repositories and other Git providers are not supported there yet. A GitLab team can keep quality gates in its own CI even though Vercel's native check is going away. Review Vercel CI's limits and pricing before switching.

The key test is not whether a new workflow starts. It is whether a real failure blocks the release or merge you intend to protect. SoyJB reviewed the official sources and wrote this migration checklist; we did not migrate your repository or inspect its branch-protection rules. Run the failure test before November 30.

Sources

Comentarios

Aún no hay comentarios. Sé el primero.

Deja un comentario