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
When I run nx release it only updates versions of the packages that are built inside dist/.
And inside the packages/* folders, Nx doesn't update the versions. It always remains same "0.0.1".
Expected Behavior
It should update version of the projects inside the packages/ folder
@mxvsh Can you share your nx.json and your project.json files for relevant libs?
If you have a look at the docs here you'll see that you have it currently set up for scenario 2 where the actual version of packages needs to be resolved either from a git tag or by fetching the latest version from the npm registry since as you noticed, the version is not written into the source directories.
If you want to change to scenario 1 you'll have to update your build targets to output to {projectRoot}/dist and adopt the packageRoot option for both the version generator and the publish executor.
It's not a bug but I understand your issue. Every team has their own way of versioning / publishing and nx is trying hard to come up with a tool that can be configured to work for everyone. If it works out the box for you, then you are very lucky :)
Current Behavior
When I run
nx release
it only updates versions of the packages that are built insidedist/
.And inside the packages/* folders, Nx doesn't update the versions. It always remains same "0.0.1".
Expected Behavior
It should update version of the projects inside the
packages/
folderGitHub Repo
No response
Steps to Reproduce
nx release
Nx Report
Failure Logs
Package Manager Version
pnpm
Operating System
Additional Information
No response
The text was updated successfully, but these errors were encountered: