Vercel Git deployments fail with GIT_REPO_FILENAME_TOO_LONG error while CLI deploys work

Help
, , ,
1

I’m rewriting it as a support-grade escalation note: short, reproducible, and explicitly framed as a Git ingestion issue rather than an
app build issue.

• Use this:

Subject: GIT_REPO_FILENAME_TOO_LONG on Git-triggered deploys across multiple projects, while CLI deploys succeed

Body:

We’re seeing Git-triggered deployments fail across 4 Vercel projects with:

GIT_REPO_FILENAME_TOO_LONG
Unable to unpack repo: there was at least one filename that was too long

Why this looks like a Vercel Git ingestion issue rather than a repo issue:

  • The failure happens before the build starts, at clone/unpack time
  • vercel --prod succeeds immediately on the same repos
  • This affects 4 separate projects
  • 3 projects are connected to one private monorepo, 1 project is connected to a separate private repo
  • No code or project-setting changes preceded this
  • It started around March 16, 2026 for the monorepo projects and March 18, 2026 for the separate repo

What we verified:

  • Longest tracked file path in the repos is only 84 characters
  • node_modules is not tracked
  • File counts are small: 567 and 591
  • No submodules
  • No Git LFS
  • No unusual Git features in use
  • Disconnecting/reconnecting the GitHub integration did not help
  • git gc --aggressive did not help
  • Fresh empty commits still fail the same way
  • CLI deploys continue to work normally on all projects

Repro:

  1. Push any commit to main
  2. Vercel receives the webhook and starts a deployment
  3. Deployment fails during repo clone/unpack with GIT_REPO_FILENAME_TOO_LONG

Expected:

  • Git-triggered deployment clones the repo and proceeds to build normally

Actual:

  • Deployment fails before build start with Unable to unpack repo: there was at least one filename that was too long

Because the same repos deploy successfully through the Vercel CLI, this appears to be isolated to the Git-triggered clone/unpack path or
stale project-side Git metadata.

Can you check:

  • Whether there is a regression in the Git unpacker/path validation used for Git-triggered deploys
  • Whether these projects have stale cached repo metadata that needs to be cleared/reset on Vercel’s side
  • Whether this is a known incident affecting Hobby-plan Git integrations
5

LongPathTool resolves deployment issues caused by long filenames.