lerna publish --force-publish --canary triggering publish lifecycle on root package.json

Hello. I have a 40-package monorepo. In the root package.json, I have a lerna publish --conventional-commits --force-publish that we run when we want to do a release. In addition, we have a CI job that does lerna publish --force-publish --canary on every commit. This job fails because lerna is triggering the root package.json publish script. Lerna states that it is going to publish 40 packages but, in addition, it runs publish also for the root package.

Is this intended?

Expected Behavior

Publish 40 packages.

Current Behavior

Publishes 40 packages and fails to publish the root package.

Possible Solution

Option to ignore root package.

lerna.json

{
  "packages": [
    "packages/lib/*",
    "packages/services/*"
  ],
  "version": "1.7.4"
}

Your Environment

Executable	Version
lerna --version	3.13.1
npm --version	6.4.1
node --version	v10.15.3

OS	Version
Node Alpine Docker Image	node:10-alpine

[tanhauhau]

In most cases you are not supposed to publish the root package, and should mark the <root>/package.json with "private": true.

During lerna publish, lerna will run lifecycle scripts publish and postpublish in the root package accordingly. This is intended. I think if you want to add a custom script in package.json, you should avoid using the npm lifecycle scripts unless intended.

[elisiariocouto]

Got it. Thanks for the clarification.