fix(docs): bypass Stack build on Vercel - #257
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. 2 Skipped Deployments
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
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
1 participant
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.
Summary
^buildedge to the full@btst/stackbundlebuild:vercelscript so the deployment seam is explicitWhy
The v3.0.0 production docs deployment failed with
BUILD_EXCEEDED_MAXIMUM_TIME. Vercel invalidated its Node 22 cache after the project moved to Node 24, thenturbo run buildcold-built@btst/stackand never reached the docs'next buildbefore the 45-minute limit.The Rollup
use clientand mixed-export messages were warnings, not the failure.Verification
packages/stack/distabsentpnpm --dir docs buildunder Node 22: passed, 56 pagespnpm --dir docs build:vercelunder Node 24: passed, 56 pagesVercel created preview deployments for both branch commits but canceled them at the project-level Ignored Build Step before producing any build logs. Production Git deployments are the remaining remote verification path.