fix: prevent duplicated Vercel monorepo root during prebuilt deploy - #33
Merged
Conversation
|
Deployment failed with the following error: Learn More: https://vercel.com/atomicdjts-projects?upgradeToPro=build-rate-limit |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Root cause
Manual LayerForge preview run #12 successfully completed application verification, token verification, Vercel project linking, configuration pull, and
vercel build.vercel deploy --prebuiltthen failed because the project path resolved as:apps/layerforge-studio/apps/layerforge-studioThe Vercel project already has
apps/layerforge-studioconfigured as its Root Directory, while the workflow also executed the Vercel CLI from that same subdirectory.Minimal correction
link,pull,build, anddeploy --prebuiltfrom the monorepo root;working-directory: ${{ matrix.path }}from returning to those four Vercel CLI steps;Test-first evidence
Red
Portfolio CI run 230 failed specifically at
Test deployment selectorafter 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:Safety boundary
VERCEL_DEPLOYMENT_ORCHESTRATION_ENABLEDremainsfalse;