chore(turbo_json): lift $TURBO_DEFAULT$ handling to turbo.json resolution
#10709
Conversation
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
Contributor
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
$TURBO_DEFAULT$ handling to turbo.json parse time$TURBO_DEFAULT$ handling to turbo.json resolution
tknickman
approved these changes
Jul 23, 2025
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.
Description
This PR moves the handling of
$TURBO_DEFAULT$to be the responsibility ofturbo.jsonresolution.Previously it was handled by our SCM module which should only be focused on SCM operations, not magical strings from Turborepo.
The changes to the daemon only affect the daemon input hashing logic which is currently disabled.
Reviewing each commit independently is suggested.
Testing Instructions
Added unit tests and existing tests.