deniz.in

Markets

Weather

Loading weather

· via Vercel blog

Vercel deprecates native lint and typecheck deployment checks, removal due November 2026

Vercel is removing its native lint and typecheck Deployment Checks, with existing checks deleted on November 30, 2026. Teams will need to run these tasks in Vercel CI, their own CI, or the Build Command instead.

Vercel deprecates native lint and typecheck deployment checks, removal due November 2026

What is being removed

According to a changelog post on the Vercel blog dated November 17, 2026, Vercel is deprecating its native lint and typecheck Deployment Checks. These are the checks that executed a repository's lint and typecheck tasks on Vercel's servers alongside deployment builds, giving teams visibility into code quality as part of the deployment process.

The shutdown happens in two steps. New lint and typecheck checks can no longer be created as of the announcement. Existing checks will keep running until November 30, 2026, at which point they are removed entirely.

Not everything is affected: Vercel states that other Deployment Checks, along with commands already running in GitHub Actions or in a project's Build Command, continue to work unchanged.

How to know if a project is affected

Per the changelog, the deprecated checks appear as Lint or Typecheck entries with Vercel listed as the provider in a project's Build and Deployment settings. Any project showing those entries needs its commands moved before the November 30 cutoff, otherwise the checks simply stop running.

Migration options

Vercel recommends moving the lint and typecheck tasks to Vercel CI or to a team's own CI workflows. To help with that, the changelog includes a ready-made prompt that can be handed to a coding agent to configure the tasks and open a pull request for review, and it points readers to the Vercel CI documentation for further details.

An alternative is to run the commands in the project's Build Command. Vercel flags two trade-offs with that approach: it could lengthen build times, and any failing command will break the deployment build outright.

One warning deserves particular attention: for checks that currently block production releases, Vercel advises teams to verify how the replacement workflow handles failures. In other words, moving the commands is only half the job. The release-blocking behavior has to be deliberately reproduced, or a failing lint or typecheck run could quietly stop gating production deployments.

Why it matters

The deprecation shifts responsibility for these quality gates off Vercel's platform and back onto teams' own pipelines. Anyone who relied on the native checks as a primary line of defense now has a hard deadline: after November 30, 2026, the checks stop running and deployments proceed without them.

The migration itself is mechanical, copying commands into CI or the Build Command, but it is not automatic, and the failure semantics need re-verification to keep existing protections intact. The change also signals where Vercel wants this work to happen: the changelog steers users toward Vercel CI first, with GitHub Actions or other CI systems as the fallback, effectively pushing build-time checks into pipelines the team itself controls.

  • #vercel
  • #continuous-integration
  • #linting
  • #typecheck
  • #deployment

Related posts