chore(ci): add diagnostic logging to vercel ignore build step#116
Merged
chore(ci): add diagnostic logging to vercel ignore build step#116
Conversation
Helps debug why 'turbo query affected' returns an empty list on Vercel even when HEAD^1..HEAD clearly touches the explorer's dependency graph (e.g. deploy for 243d43e on develop was canceled despite the commit changing apps/explorer/** and apps/core/**). Logs git state, changed files, and any restored .turbo cache before running the turbo query.
|
The latest updates on your projects. Learn more about Vercel for GitHub. 5 Skipped Deployments
|
VmMad
approved these changes
Apr 21, 2026
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
2 participants
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.
Context
The explorer deploy for commit
243d43eondevelopwas canceled by the Ignored Build Step, despite the commit clearly touchingapps/explorer/**andapps/core/**. The Vercel log showed:Investigation so far
Ran the exact command locally against the same commit — could not reproduce:
git clone --depth=10 --branch develop+pnpx turbo query affected --packages iota-explorer --base=HEAD^1 --exit-code→ returnslength: 1, exit 1 (would build). ✅pnpm install.2.9.0,2.9.1,2.9.2,2.9.3,2.9.4,2.9.5,2.9.6— all correctly detectiota-exploreras affected.Remaining suspects, all Vercel-specific and not reproducible from here:
.turbocache from the previous deployment (log showsRestored build cache from previous deployment (7Eia…)immediately before the script runs).origin/HEAD, odd branch state) that could makeHEAD^1resolve to something unexpected.Change
Adds diagnostic logging to
scripts/vercel/ignore-build-step-base.shso the next canceled deploy shows:HEADandHEAD^1SHAsHEAD^1..HEAD.turbo/stateWith that output from a real Vercel run we can point at the actual cause instead of guessing. Once we know, the logging will be replaced with a targeted fix.