Repository navigation
fix(build): stop unnecessary Vercel builds across the monorepo - #555
Merged
Merged
Conversation
Merged
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.
A gateway-only change currently rebuilds the web app, CommonLab, and docs on feature branches, staging, main, and staging sync. These three projects account for $53.49 of the last invoice’s $54.91 build CPU charge.
Only automatically deploy staging and main. Compare each app with its last successful deployment on that branch and include its transitive workspace dependencies. Skip backend/infrastructure-only changes and staging syncs whose trees are unchanged; build safely when history is missing. Keep shared lockfile/toolchain changes as build inputs.
Add a dry-run-first Vercel settings reconciler to enable native unaffected-project skipping, use Basic build machines, and queue builds instead of paid on-demand concurrency, preserving every function/runtime setting. These controls affect future builds only. Manual deployments remain available.
Validation: 20 tests passed, including multi-commit releases, transitive dependencies, deleted/renamed files, missing history, fetching the exact prior commit in a shallow clone, and Vercel exit codes. Configuration keys checked against Vercel’s published schema. Replaying the latest 100 deployments per app estimates 82% less aggregate build time (historical estimate, not a guaranteed invoice reduction).
Staging verification: confirm the affected apps build on Basic, staging routes respond, and same-tree/unrelated changes skip. Promotion will use staging → main with a merge commit.