lerna: lerna publish --force-publish is not working
lerna publish --force-publish is not working with latest. it used to work with lerna@3.0.6. Updated today to 3.2.1 and observed that following command doesn’t do force publish
lerna publish --force-publish=package1
Expected Behavior
Command should start publish
Current Behavior
Not publishing on force publishing
Possible Solution
Steps to Reproduce (for bugs)
lerna.json
<!-- Please paste your `lerna.json` here -->
lerna-debug.log
<!-- If you have a `lerna-debug.log` available, please paste it here -->
<!-- Otherwise, feel free to delete this <details> block -->
Context
Your Environment
| Executable | Version |
|---|---|
lerna --version |
3.2.1 |
npm --version |
5.6.0 |
yarn --version |
1.6.0 |
node --version |
8.10.0 |
| OS | Version |
|---|---|
| Ubuntu | latest |
Edit : It was 3.0.0-beta.17 not 3.0.6 previously from where I updated to 3.2.1
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 2
- Comments: 20 (7 by maintainers)
I’m not sure what lerna is supposed to publish when nothing has changed? This is one reason I dislike
--force-publishin general: it leads to a false sense of purpose. If a given package didn’t change, lerna won’t publish it. Lerna certainly won’t try to publish anything if there have been zero commits since the last release.@evocateur in my recent experience,
--force-publishwould be nice because lerna will refuse to publish unpublished work if it has previously created the commit/tag but failed to publish. I’m now stuck in a loop where I have to delete tags and commits 😦I’m so close to deleting the
--force-publishoption entirely, it has given me nothing but pain, recently.Convince me to keep it by contributing a PR to “fix” it. I’m done trying to make it work.
This option was removed? Can’t find it in the latest docs anymore.
@runspired from-package is what you’re looking for.