fix(ci): Remove unused turbo remote cache env vars #33030
Merged
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.
Cleanup #32617
Remove unused
turbo
env vars which are not needed since the Next.js core monorepo is not using remote caching (yet), just local fs caching.For those curious, the
nextjs
team andnextjs
project listed asTURBO_TEAM
andTURBO_PROJECT
were forturbo
< v1.x which talked to Turborepo's pre-acquisition and soon-to-be-shutdown legacy remote caching service. Lastly, for those curious, theTURBO_PROJECT
variable and its sister--project
flag were deprecated in v1.x as well.@timneutkens Please remove
TURBO_TOKEN
from the Next.js repo's GitHub secrets for good security hygiene