Skip to content

Docs preview CI fails repo-wide: Vercel 15,000-file upload cap exceeded #91

Description

@cafzal

What's happening

The preview job (Docs preview workflow, .github/workflows/docs-preview.yml) fails on every recent PR with:

Error: Invalid request: `files` should NOT have more than 15000 items, received 16305.
Try using `--archive=tgz` to limit the amount of files you upload.

The count climbs as the site grows (16,270 → 16,305 across the last couple of runs).

Evidence it's repo-wide, not PR-specific

So the deployed file set recently crossed Vercel's hard 15,000-file upload cap. It's independent of any individual PR's content — template-content PRs add a handful of files, nowhere near the cap.

Impact

  • preview is red on every new PR. It is not a required check (the main branch is unprotected), so it does not block merges — but it's persistent red noise and would mask a genuine preview regression.

Root cause

The Vercel deploy step uploads the full relationalai-docs checkout as loose files — the external docs site plus npm install node_modules plus the synced templates — which together exceed the 15k-file cap. The deploy goes through aldenquimby/deploy-to-vercel-action@v2.

Suggested fixes (for the owners to evaluate)

  1. --archive=tgz on the Vercel deploy (Vercel's own suggestion) — but confirm aldenquimby/deploy-to-vercel-action@v2 forwards extra CLI args; if not, switch that step to a raw vercel deploy --archive=tgz ….
  2. .vercelignore / build-output deploy in the relationalai-docs repo so node_modules and build artifacts aren't uploaded as loose files.

cc @somacdivad @jablonskidev — flagging as the docs-preview pipeline owners; happy to open a PR for option 1 if you'd like, but it touches shared CI and can't be validated without the Vercel secrets.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions