Skip to content

Remove the Cache Components deployment-test alias - #99446

Draft
gnoff wants to merge 1 commit into
canaryfrom
jstory/remove-cache-components-deploy-alias
Draft

gnoff wants to merge 1 commit into
canaryfrom
jstory/remove-cache-components-deploy-alias

Conversation

@gnoff

@gnoff gnoff commented Sep 29, 2026

Copy link
Copy Markdown
Contributor

Summary

Remove NEXT_PRIVATE_EXPERIMENTAL_CACHE_COMPONENTS to simplify how deployment tests enable Cache Components. Capture __NEXT_CACHE_COMPONENTS in the generated test config instead, preserving deployment coverage and explicit config overrides without a separate environment-variable alias.

Verification

  • pnpm test-unit test/unit/next-deploy-failure/next-deploy-failure.test.ts --runTestsByPath --runInBand — 19 tests passed.
  • Loaded nine generated configs in fresh processes: enabled, disabled, and unset test flags crossed with enabled, disabled, and unset cacheComponents config. Flag propagation and explicit config overrides were preserved.
  • Live Vercel deployment validation was not run.

Remove NEXT_PRIVATE_EXPERIMENTAL_CACHE_COMPONENTS to simplify how deployment tests enable Cache Components. Capture __NEXT_CACHE_COMPONENTS in the generated test config instead, preserving deployment coverage and explicit config overrides without a separate environment-variable alias.
@github-actions

github-actions Bot commented Sep 29, 2026 •

Copy link
Copy Markdown
Contributor

Failing CI jobs

Commit: 654cad9 | About building and testing Next.js

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant