When SDK package has changes, but types package doesn't and I run nx release it doesn't replace its dependency version to a semantic version (f.e. 1.0.0).
When both of them have changes - all is good, types version is bumped and in SDK workspace is replaced correctly.
Expected Behavior
I'd expect it to always replace workspace dependency to the version that types package is currently in.
No changes are done to package-types dependency it just bumps SDK version when testing locally with pnpx nx release --verbose --yes --dry-run
### Package Manager Version
9.9.0
### Operating System
- [X] macOS
- [ ] Linux
- [ ] Windows
- [ ] Other (Please specify)
### Additional Information
I'm not entirely sure if it's a bug or feature request, or maybe it's related to pnpm? But I've tried for example `pnpm pack` and it replaced dependency version correctly. I assume nx under the hood uses pacakge manager publish command?
Maybe I'me just missing some sort of configuration in `nx.json`?
Current Behavior
I have two packages: SDK and types.
SDK has a direct dependency to types through workspace protocol:
When SDK package has changes, but types package doesn't and I run
nx release
it doesn't replace its dependency version to a semantic version (f.e. 1.0.0).When both of them have changes - all is good, types version is bumped and in SDK
workspace
is replaced correctly.Expected Behavior
I'd expect it to always replace
workspace
dependency to the version that types package is currently in.Attaching my nx.json for reference:
Maybe I'm missing some sort of onfiguration?
GitHub Repo
No response
Steps to Reproduce
workspace
nx release
workspace
dependency is not replacedNx Report
Failure Logs
No changes are done to
package-types
dependency it just bumps SDK version when testing locally withpnpx nx release --verbose --yes --dry-run