fix(core): add migration to set useLegacyCache by default#28454
fix(core): add migration to set useLegacyCache by default#28454JamesHenry merged 2 commits intomasterfrom
useLegacyCache by default#28454Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎ 1 Skipped Deployment
|
☁️ Nx Cloud ReportCI 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
Sent with 💌 from NxCloud. |
a24ec2c to
22f93ad
Compare
|
Is it possible to migrate an existing workspace to the db cache instead? Can't seem to find this documented anywhere. |
|
@sleeyax Just migrate to Nx 20 as normal, and remove this |
|
Gotcha, thanks for the info! |
|
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. |
Current Behavior
Existing workspaces that migrate to v20 use the db cache by default.
Expected Behavior
Existing workspaces that migrate to v20 have
useLegacyCacheset to true. Unless they specifically hadenableDbCachefrom previous versions of Nx. All new workspaces will not haveuseLegacyCacheset by default.Related Issue(s)
Fixes #