Error "Could not execute command because the task graph has a circular dependency" after upgrading from 19.3.1 to 19.6.3

[Robouste]

Current Behavior

The app won't build anymore

Expected Behavior

The app should build

GitHub Repo

No response

Steps to Reproduce

From a project with nx 19.3.1 and Angular 18.0.2

1. nx migrate latest
2. nx migrate --run-migrations
3. nx affected --targets=test,build,lint

Nx Report

Node           : 18.19.1
OS             : win32-x64
Native Target  : x86_64-windows
npm            : 8.19.3

nx                 : 19.6.3
@nx/js             : 19.6.3
@nx/jest           : 19.6.3
@nx/linter         : 19.6.3
@nx/eslint         : 19.6.3
@nx/workspace      : 19.6.3
@nx/angular        : 19.6.3
@nx/cypress        : 19.6.3
@nx/devkit         : 19.6.3
@nx/esbuild        : 19.6.3
@nx/eslint-plugin  : 19.6.3
@nx/nest           : 19.6.3
@nx/node           : 19.6.3
@nx/storybook      : 19.6.3
@nrwl/tao          : 19.6.3
@nx/web            : 19.6.3
@nx/webpack        : 19.6.3
typescript         : 5.5.4
---------------------------------------
Registered Plugins:
@nx/webpack/plugin
---------------------------------------
Community plugins:
@auth0/auth0-angular             : 2.2.3
@fortawesome/angular-fontawesome : 0.15.0
@ngrx/effects                    : 18.0.2
@ngrx/entity                     : 18.0.2
@ngrx/router-store               : 18.0.2
@ngrx/schematics                 : 18.0.2
@ngrx/store                      : 18.0.2
@ngrx/store-devtools             : 18.0.2
@storybook/angular               : 8.2.9
ng2-charts                       : 6.0.1

Failure Logs

NX   Affected criteria defaulted to --base=origin/develop --head=HEAD

NX   Could not execute command because the task graph has a circular dependency

Package Manager Version

No response

Operating System

• [ ] macOS
• [ ] Linux
• [X] Windows
• [ ] Other (Please specify)

Additional Information

Nothing other than the package.json has changed. The application is huge and using nx graph generates a very dense spider web, making it nearly impossible to identify the issue. (if there is any, since it was working fine before the migration).

[mxvsh]

same here