fix(core): fix cli to properly handle the migrate command after the packages consolidation

[leosvelperez]

Current Behavior

When running the migrate command from a version older than v13.9.0 to latest, the command doesn't run properly and keeps opening new processes to run itself.

This happens because in the old versions tao migrate will be run, but the migrate command installs the latest version of @nrwl/tao which now defers the execution to the nx package and this one is only handling _migrate as the command for running the migration but not migrate. Because of that, it doesn't identify it as the migration command and it continues the execution which ends up running the migrate command again.

Expected Behavior

Migrations should run successfully.

Related Issue(s)

Fixes #9345

[nx-cloud]

☁️ Nx Cloud Report

CI ran the following commands for commit 1bdcd7f. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

---

✅ Successfully ran 7 targets

• nx affected --target=build --base=fd980443f26fc202b1df01425ca6384c757e7c3e --head=1bdcd7f3055cbdd05d9810fedbf85e15ec47cff2 --parallel=3
• nx affected --target=e2e --base=fd980443f26fc202b1df01425ca6384c757e7c3e --head=1bdcd7f3055cbdd05d9810fedbf85e15ec47cff2 --exclude=e2e-detox,e2e-js,e2e-next,e2e-workspace-create,e2e-workspace-integrations,e2e-workspace-core,e2e-react,e2e-web,e2e-angular-extensions,e2e-angular-core,e2e-cli,e2e-nx-plugin,e2e-cypress,e2e-node,e2e-linter,e2e-jest,e2e-a...
• nx affected --target=e2e --base=fd980443f26fc202b1df01425ca6384c757e7c3e --head=1bdcd7f3055cbdd05d9810fedbf85e15ec47cff2 --exclude=e2e-storybook,e2e-react-native,e2e-detox --parallel=1
• nx affected --target=lint --base=fd980443f26fc202b1df01425ca6384c757e7c3e --head=1bdcd7f3055cbdd05d9810fedbf85e15ec47cff2 --parallel=3
• nx affected --target=test --base=fd980443f26fc202b1df01425ca6384c757e7c3e --head=1bdcd7f3055cbdd05d9810fedbf85e15ec47cff2 --parallel=1
• nx build typedoc-theme
• nx run-many --target=build --all --parallel=8 --exclude=docs,nx-dev-data-access-documents,nx-dev-e2e,nx-dev,nx-dev-feature-analytics,nx-dev-feature-conf,nx-dev-feature-doc-viewer,nx-dev-feature-search,nx-dev-feature-storage,nx-dev-feature-versions-and-flavors,nx-dev-ui-commands,nx-dev-ui-common,nx-dev-ui-home,nx-dev-ui-member-card,nx-dev-ui-sponsor...

---

Sent with 💌 from NxCloud.

[vercel]

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/nrwl/nx-dev/ZMmMpNrNXP2QbNXTmwrZbWvbb9DP
✅ Preview: Canceled

[matt-ganz]

I just migrated from Nx 13.1.3 to 14.0.0 and noticed that my nx migrations were failing silently. Then i saw that the migration didn't update nrwl/tao so my old version was still there (13.1.3). i manually updated tao to 14.0 and ran npm install and nx migrations and then it started working. but when i look now at my package.json i see that tao is now gone. i'm guessing Nx 14 moved away from Tao. but why am i still getting the node processes error (i mean my builds are still hanging).

[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.