Regression Error with Nx 15, yarn -p nx run-many

I'm submitting a...


[x] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request
[ ] Other... Please describe:

Current behavior

Our Project's Github Action pipeline broke unexpectedly after the newest release was published on 01.06.2023. @v2.5.1

Expected behavior

New releases should be backward compatible with non-major releases.

Minimal reproduction of the problem with instructions

Our Angular App is not yet migrated to Nx 16, currently using Nx 15, but using the newest Github Action with uses: e-square-io/nx-distributed-task@v2

What is the motivation/use case for changing the behavior?

No changes were introduced on our side.

The observed difference between version 2.4.0 and 2.5.1 is Before: yarn -p @nrwl/cli nx run-many After: yarn -p nx run-many

/home/runner/actions-runner/_work/_tool/node/16.13.0/x64/bin/yarn -p @nrwl/cli nx run-many --projects=prediction --skip-nx-cache=false --prod --localize=true --target=build --parallel=3

  /home/runner/actions-runner/_work/_tool/node/16.13.0/x64/bin/yarn -p nx run-many --projects=dashboard --skip-nx-cache=false --prod --localize=true --target=build --parallel=3
  yarn run v1.22.19
  error Command "run-many" not found.

Environment


- Nx version: 15.6.2
- Node version: 16.13.0
- Platform:  Ubuntu Runner

e-square-io / nx-github-actions