Skip to content
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

Publish an initial v1.0.0 with conventional commits #2739

Open
m-mayank opened this issue Oct 16, 2020 · 1 comment
Open

Publish an initial v1.0.0 with conventional commits #2739

m-mayank opened this issue Oct 16, 2020 · 1 comment

Comments

@m-mayank
Copy link

m-mayank commented Oct 16, 2020

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

@achingbrain
Copy link
Contributor

I'm not sure how to go from 0.x.x to x.x.x in CI, but locally it can be done by:

  1. Change the version in package.json for the packages to publish from 0.x.x to 1.0.0-1 as per this comment
  2. Graduate them to a release with lerna version --conventional-graduate my-package,my-other-package (will create release notes etc on GitHub)
  3. Finally publish them to npm with lerna publish from-package

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants