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
Considering with the recent changes, now lerna publish does not entertains Breaking Change when a given package is in 0.x.x state. The feature is quite useful, but with this I could not found a way to have a Initial release for a given package in an automated CI ecosystem.
Also the same becomes a problem when we are in monorepo having multiple packages, and then when we want to add a new package.
The only option i could find as of now is to commit a package with v1.0.0 and the lerna publish releases it as v1.0.1
Executable
Version
lerna --version
v3.22.1
npm --version
v6.12.0
node --version
v12.13.0
Note: the same issue was highlighted in #2325, but has no answer yet and the issue seems to be closed
The text was updated successfully, but these errors were encountered:
Considering with the recent changes, now lerna publish does not entertains Breaking Change when a given package is in 0.x.x state. The feature is quite useful, but with this I could not found a way to have a Initial release for a given package in an automated CI ecosystem.
Also the same becomes a problem when we are in monorepo having multiple packages, and then when we want to add a new package.
The only option i could find as of now is to commit a package with
v1.0.0
and thelerna publish
releases it asv1.0.1
lerna --version
npm --version
node --version
Note: the same issue was highlighted in #2325, but has no answer yet and the issue seems to be closed
The text was updated successfully, but these errors were encountered: