-
-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Latest version(v5.1.1) not bumping the version of a project if the changes made to the dependency. #785
Comments
I'll reopen it once I am fully sure that issue exists, currently I can't reproduce it every time. So not sure what is causing this issue. In my actual project this issue is always there but not in the repro repository. |
Reopening the bug as now I'm sure that it will always fail version bump if you follow the repro steps. |
+1 on this...we're experiencing the same issue. Would be great if this could be fixed |
Maybe I can raise my question here: would this help? #816 |
The issue still exists, although a possible solution exists with #816. We would also be interested in the PR being merged. That would really help us because since the update to NX 19 our pipeline often fails. |
I'd prefer not adding an extra option for that and simply track deps with prerelease. |
In my workspace when I am making changes to the feature libs of my app and committing changes after that when I run target to bump the version its not increasing the version of my app. It was working fine till 4.2.x.
I have reproduced the issue in the following repro repo:
https://github.com/ak274/semver
My App project.json for version target:
Steps to reproduce:
libs/demo/feature-lib
2) commit the feature withangular commit convention
3)push
commit to the originmaster
demo
appExpected behavior:
As I have made changes to a feature lib which is a dependency of app, It should bump the version for my app.
The text was updated successfully, but these errors were encountered: