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

How to use the canary release? #702

Closed
nicojs opened this issue Mar 21, 2017 · 6 comments · Fixed by #705
Closed

How to use the canary release? #702

nicojs opened this issue Mar 21, 2017 · 6 comments · Fixed by #705
Assignees

Comments

@nicojs
Copy link

nicojs commented Mar 21, 2017

Expected Behavior

I'm trying the new canary release in order to use the new conventional-changelog option (via conventional-changelog/conventional-changelog#168)

npm i -D lerna@canary
./node_modules/.bin/lerna init
./node_modules/.bin/lerna publish  --skip-npm --skip-git --conventional-commits

I expect the changelog to be updated

Current Behavior

I get this error:

Lerna major version mismatch: The current version of lerna is 2.0.0-beta.38-38-g8c7deb7, but the Lerna version in `lerna.json` is 2.0.0-beta.38-38-g8c7deb7. You can either run `lerna init` again or install `lerna@2.0.0-beta.38-38-g8c7deb7`.

Versions:

$ ./node_modules/.bin/lerna --version
2.0.0-beta.38-38-g8c7deb7

$ npm --version
3.8.2

$ node --version
v7.5.0
@vovacodes
Copy link
Contributor

@nicojs just set the "lerna" field in your lerna.json to 2.0.0-beta.38-38-g8c7deb7 and it should work

@evocateur
Copy link
Member

Huh, theoretically lerna init should have updated lerna.json appropriately. Investigating...

@evocateur
Copy link
Member

Definitely a bug, didn't test against the git describe format I've been using for the canary releases. 😬

@evocateur
Copy link
Member

@nicojs The latest canary (lerna@2.0.0-beta.38-40-g203f7eb) should work now.

@nicojs
Copy link
Author

nicojs commented Mar 22, 2017

Thanks! I'll give it a spin right now

@lock
Copy link

lock bot commented Dec 28, 2018

This thread has been automatically locked because there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Dec 28, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants