nx release version
is not correctly updating all of the packages in the dependency graph
#29672
Open
2 of 4 tasks
Labels
Current Behavior
nx release version --specifier=patch --projects={some-package-in-dependency-graph}
is not correctly recursively updating all of the packages in the dependency graph that depend on the specified project(s).The project in the repo (https://github.com/asinning/nx-release-version-bug) has the structure:
graph-top
We would expect
nx release version --specifier=patch --projects=dep-d
to bump the patch version for all 5 packages in the project; however, it only updates dep-d, dep-c and dep-b.We would expect
nx release version --specifier=patch --projects=dep-c
to bump the patch version for all the packages in the project except for dep-d; however, it only updates dep-c, dep-b and dep-a.We would expect
nx release version --specifier=patch --projects=dep-b
to bump the patch version for dep-b, dep-a and graph-top, and this is exactly what it does.Even if we specify three packages in the middle of the graph, we do see the top most package updated.
npx nx release version --specifier=patch --projects=dep-a,dep-b,dep-c
only updates deps a, b and c.However, and this is most curious of them all,
npx nx release version --specifier=patch --projects=dep-a,dep-b,dep-c,dep-d
will update all 5 packages, even though graph-top is not in the list.In conclusion, it appears that the command
nx release version
tends to have a depth limit of 2; however, the exact pattern is difficult to determine.Expected Behavior
I would expect all packages in the repo that are dependent on the specified project to have their patch version bumped.
GitHub Repo
https://github.com/asinning/nx-release-version-bug
Steps to Reproduce
See above, see README in repo https://github.com/asinning/nx-release-version-bug/blob/main/README.md
Nx Report
Failure Logs
Package Manager Version
No response
Operating System
Additional Information
No response
The text was updated successfully, but these errors were encountered: