Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Lerna publish flag `--conventional-commits` doesn't work with `--npm-tag` flag
See original GitHub issueExpected Behavior
I have one project that have one trunk branch to release with dist-tag latest. For next major version, there is another branch task/v3 to release with dist-tag v3.
The script is like below:
lerna publish --conventional-commits --exact --npm-tag=v3
It is expected to publish all packages with conventional-commits and on dist-tag v3.
Current Behavior
The script failed with message like below:
npm ERR! code ELIFECYCLE npm ERR! errno 1 npm ERR! publish:v3:
lerna publish --conventional-commits --exact --npm-tag=v3npm ERR! Exit status 1
Possible Solution
It looks that the two flags --conventional-commits and --npm-tag are not compatible.
Your Environment
| Executable | Version |
|---|---|
lerna --version |
3.0.0-beta.21 |
npm --version |
5.6.0 |
node --version |
v6.13.0 |
| OS | Version |
|---|---|
| macOS Sierra | 10.13.5 |
Issue Analytics
- State:
- Created 5 years ago
- Comments:15 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Would you believe I had no tests around the presence or absence of
publishConfig.tag?Coincidentally, I’m working on making
--npm-tagoverridepublishConfig.tagwhen it is notlatest, which I think makes more sense, especially in the--canarycase.