You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not actually sure what tool is doing what job here. But during our release process all "workspace:" references gets updated to the new actual version. So "workspace:" might for example get replaced by "8.4.5".
When I upgraded from nx v19.8.14 to v20.3.0 this behavior broke. Most "workspace:" references were correctly updated, but a couple were missed, and ended up as "workspace:" in our published packages, breaking installation of those packages.
Upgrading to v20.3.1 did not solve the problem. Still the same packages not getting their version set correctly.
Upgrading to v20.3.2 however did fix the issue. But reading the changelog it's not immediately clear to me exactly how it was fixed or what PR fixed it.
So now I have two questions:
Is this an nx issue only, or is it an issue with how nx works with some of the other tools I mentioned (yarn or lerna)
What PR fixed the issue? I would feel more confident in marking this issue as resolved on our side if I knew what actually fixed it 😅
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Not actually sure what tool is doing what job here. But during our release process all "workspace:" references gets updated to the new actual version. So "workspace:" might for example get replaced by "8.4.5".
When I upgraded from nx v19.8.14 to v20.3.0 this behavior broke. Most "workspace:" references were correctly updated, but a couple were missed, and ended up as "workspace:" in our published packages, breaking installation of those packages.
Upgrading to v20.3.1 did not solve the problem. Still the same packages not getting their version set correctly.
Upgrading to v20.3.2 however did fix the issue. But reading the changelog it's not immediately clear to me exactly how it was fixed or what PR fixed it.
So now I have two questions:
Beta Was this translation helpful? Give feedback.
All reactions