Closed overbit closed 3 years ago
Thanks for reporting this!
This issue was solved in https://github.com/nrwl/nx/pull/6252 and it'll be released in the next patch version. In the meantime, if you don't want to wait and want to proceed with the migration, you can make sure in your nx.json
you have the default
task runner with the options
property specified inside tasksRunnerOptions
, something like:
...
"tasksRunnerOptions": {
"default": {
"runner": "@nrwl/workspace/tasks-runners/default",
"options": {
"cacheableOperations": ["build", "test", "lint", "e2e"]
}
}
},
...
Please note that's an example, if you're using Nx Cloud, the task runner and the options will be different, but from what you're reporting, it seems you don't have the default
task runner defined.
I'm closing this one, the fix was released as part of Nx 12.6.0.
This issue has been closed for more than 30 days. If this issue is still occuring, please open a new issue with more recent context.
Current Behaviour
Upgrade Nx to the current latest version 12.5.7 through the
nx migrate latest
process fails when applies migrations.Expected Behaviour
Successful upgrade to latest version of nx.
Steps to Reproduce
From nx version 12.0.8, follow the guide to upgrade nx:
Failure Logs
Environment