Skip to content

fix: prevent duplicated Vercel monorepo root during prebuilt deploy - #33

Merged
atomicdjt merged 3 commits into
mainfrom
fix/vercel-monorepo-root-2026-07-17
Jul 17, 2026
Merged

fix: prevent duplicated Vercel monorepo root during prebuilt deploy#33
atomicdjt merged 3 commits into
mainfrom
fix/vercel-monorepo-root-2026-07-17

Conversation

@atomicdjt

@atomicdjt atomicdjt commented Jul 17, 2026

Copy link
Copy Markdown
Owner

Root cause

Manual LayerForge preview run #12 successfully completed application verification, token verification, Vercel project linking, configuration pull, and vercel build.

vercel deploy --prebuilt then failed because the project path resolved as:

apps/layerforge-studio/apps/layerforge-studio

The Vercel project already has apps/layerforge-studio configured as its Root Directory, while the workflow also executed the Vercel CLI from that same subdirectory.

Minimal correction

  • run Vercel link, pull, build, and deploy --prebuilt from the monorepo root;
  • leave application verification scoped by the manifest command;
  • leave the Vercel project configuration unchanged;
  • add a regression test that prevents working-directory: ${{ matrix.path }} from returning to those four Vercel CLI steps;
  • include all deployment workflow regression tests in the existing CI command.

Test-first evidence

Red

Portfolio CI run 230 failed specifically at Test deployment selector after the new regression test detected the four subdirectory-scoped Vercel CLI steps. Documentation and Vercel policy checks passed before the expected failure.

Green

Fresh verification on head 756ff369fd23ffc1cad5a6f1c6e571ccc691f05f:

  • Portfolio CI run 231: success
    • documentation links
    • deployment policy
    • selector and workflow regression tests
    • lint
    • typecheck
    • application tests
    • all application builds
  • ProcessHarbor Pro Verify run 68: success
  • Portfolio Vercel Readiness run 107: success
  • Vercel Affected Deployment Plan run 16: success; deployment skipped because pull requests remain plan-only

Safety boundary

  • VERCEL_DEPLOYMENT_ORCHESTRATION_ENABLED remains false;
  • no deployment was run from this pull request;
  • no production alias changed;
  • no Vercel project settings changed;
  • no application source changed.

@vercel

vercel Bot commented Jul 17, 2026

Copy link
Copy Markdown

Deployment failed with the following error:

Resource is limited - try again in 24 hours (more than 100, code: "api-deployments-free-per-day").

Learn More: https://vercel.com/atomicdjts-projects?upgradeToPro=build-rate-limit

@atomicdjt
atomicdjt marked this pull request as ready for review July 17, 2026 20:59
@atomicdjt
atomicdjt merged commit 7cff7fd into main Jul 17, 2026
5 of 13 checks passed
@atomicdjt
atomicdjt deleted the fix/vercel-monorepo-root-2026-07-17 branch July 17, 2026 20:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant