Major Release for BREAKING CHANGE #3982
Unanswered
yeshamavani
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
In my Lerna monorepo, a commit message including a "BREAKING CHANGE" was applied to all packages, yet only a few received a major version release, while the remainder were updated with a minor version. What could be the reason for this discrepancy?
I am using npm workspaces and use lerna for publishing packages to npm registry.
My Repository - https://github.com/sourcefuse/loopback4-microservice-catalog
I follow conventional commit guidelines
My PR - sourcefuse/loopback4-microservice-catalog#2047
here I have added the BREAKING CHANGE footer as well
based on this all the packages affected here should have a major version release but instead only a few have major version while the rest have minor version release
even though they were a part of the same commit message .
This is the release by lerna - sourcefuse/loopback4-microservice-catalog@3ddb407
I use "lerna version --yes --ci --conventional-commits" and "lerna publish from-package --yes" to version and publish my packages. https://github.com/sourcefuse/loopback4-microservice-catalog/blob/master/.github/workflows/release.yml
Beta Was this translation helpful? Give feedback.
All reactions