Stuck on an issue?

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.

force-publish doesn't work as expected

See original GitHub issue

https://github.com/lerna/lerna/tree/master#--force-publish-packages

This will skip the lerna updated check for changed packages and forces a package that didn’t have a git diff change to be updated.

When I use --force-publish Lerna adds all lerna updated packages to the package I chose.

Issue Analytics

State:
Created 5 years ago
Comments:7 (1 by maintainers)

Top GitHub Comments

3reactions

kaorecommented, Jun 25, 2018

Hi,

Our project has several dozens of loosely coupled packages. It would be a pity to have to update the version of each and every package of the repo everytime one of them changes slightly - this tends to happen several times everyday. On 2.x.x, we just specify a scope and this fits our need well, but I understand that if we update this would no longer be possible.

What would the right approach be in our case?

2reactions

bertho-zerocommented, Jun 25, 2018

Ok I understand, maybe we could add an option that does that? I’m not the only one to request this and it is true that often when I publish a patch version it is not necessary to publish a patch version in all that depends on it.