Fix NEXT_PUBLIC_
environment variables in cache
#291
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.
Fixes #290.
Changes
NEXT_PUBLIC_VERCEL_URL
withVERCEL_URL
to avoid inliningNEXT_PUBLIC_SANITY_*
to Turborepopipeline.build.env
cache keyTesting
Confirm deployment logs show that server-side API calls are going to the current deployment, even when the site build was from Full Turbo cache.