fix(core): add migration to set useLegacyCache by default

[Cammisuli]

Current Behavior

Existing workspaces that migrate to v20 use the db cache by default.

Expected Behavior

Existing workspaces that migrate to v20 have useLegacyCache set to true. Unless they specifically had enableDbCache from previous versions of Nx. All new workspaces will not have useLegacyCache set by default.

Related Issue(s)

Fixes #

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment

Name	Status	Preview	Updated (UTC)
nx-dev	⬜️ Ignored (Inspect)	Visit Preview	Oct 15, 2024 7:14pm

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 09a7fce. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 4 targets

• nx affected --targets=lint,test,build,e2e,e2e-ci --base=e0f9a5c5309f923fc3b3c9b39cc74f33e7b5803b --head=09a7fce23db7d8f347c98a45cc6a6f4ad3a94289 --parallel=3
• nx run-many -t check-imports check-commit check-lock-files check-codeowners documentation --parallel=1 --no-dte
• nx-cloud record -- nx format:check --base=e0f9a5c5309f923fc3b3c9b39cc74f33e7b5803b --head=09a7fce23db7d8f347c98a45cc6a6f4ad3a94289
• nx documentation --no-dte

---

Sent with 💌 from NxCloud.

[sleeyax]

Is it possible to migrate an existing workspace to the db cache instead? Can't seem to find this documented anywhere.

[JamesHenry]

@sleeyax Just migrate to Nx 20 as normal, and remove this useLegacyCache flag from your nx.json if it is present. I would advise running nx reset any time after your make changes related to the cache (such as adding or removing this flag).

[sleeyax]

Gotcha, thanks for the info!

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.