Question About Nx Release Behavior with Dependent Libraries

[markusvoelk-zr]

Hi there,

I have a question regarding how Nx handles releases involving multiple libraries.

Scenario:

• I have two libraries: lib-a (v1.0.0) depends on lib-b (v1.0.0), and both have been published.
• I add a new feature to lib-b, but I don't release a new version - so lib-b remains at v1.0.0.
• Then, I start using that new feature in lib-a.
• I release lib-a as v2.0.0. However, its package.json still lists dependency lib-b at v1.0.0.
• As a result, the published version of lib-a (v2.0.0) is broken, because the feature it uses in lib-b isn’t available in the released version of lib-b.

Question:

How does Nx typically handle this situation?

I’m aware of the --updateDependents flag, which triggers releases for all dependents when a library is updated. However, in my case, I’m looking for the opposite: I’d like Nx to ensure that all dependencies of lib-a are released first—before releasing lib-a.

I hope that makes sense.
Thanks in advance for your help!