Nx release command is not bumping all the dependents chain
moroale93 opened this issue · 4 comments
moroale93 commented
Current Behavior
I set up a new NX repository containing four libraries, each depending on the one above it in a cascading (waterfall) structure, as illustrated in the attached image.
When I make a change to mylib4
, the mylib
library version and the indirect dependent does not have their versions bumped during the release process. I expected mylib
to reflect a version change, just like mylib2
.
But you will see something like the following:
Expected Behavior
I expect mylib4
changes to include also a version update for @my-workspace/mylib2
:
- "version": "0.0.1",
+ "version": "0.1.0",
"dependencies": {
- "@my-workspace/mylib2": "0.0.1"
+ "@my-workspace/mylib2": "0.1.0"
}
GitHub Repo
https://github.com/moroale93/nx-issue-test
Steps to Reproduce
- Install dependencies:
npm install
- modify something on
mylib4
(like the exported variable value). - commit those changes (locally)
- run the release command (dry run for example)
yarn nx release --skip-publish --dry-run --verbose
Nx Report
➜ nx-issue-test git:(main) ✗ nx report
NX Report complete - copy this into the issue template
Node : 18.20.4
OS : darwin-arm64
Native Target : aarch64-macos
npm : 10.7.0
nx (global) : 20.2.2
nx : 20.2.2
@nx/js : 20.2.2
@nx/jest : 20.2.2
@nx/eslint : 20.2.2
@nx/workspace : 20.2.2
@nx/devkit : 20.2.2
@nx/eslint-plugin : 20.2.2
@nx/module-federation : 20.2.2
@nx/react : 20.2.2
@nx/web : 20.2.2
@nx/webpack : 20.2.2
typescript : 5.6.3
---------------------------------------
Registered Plugins:
@nx/webpack/plugin
@nx/eslint/plugin
@nx/jest/plugin
➜ nx-issue-test git:(main) ✗
Failure Logs
no failures
Package Manager Version
No response
Operating System
- macOS
- Linux
- Windows
- Other (Please specify)
Additional Information
No response