Upgrading version of package used on monorepo root

Expected Behavior

Upgrade the package version like it happens if it is used inside another workspace package.

Current Behavior

Doesn’t do it.

Possible Solution

Don’t know.

Steps to Reproduce (for bugs)

Example: https://github.com/tunnckoCoreHQ/hela/blob/v3-next/package.json#L26 I’m using one of my monorepo packages as a dependency to the monorepo root. Usually when new release is done, Lerna updates the package version if this package is used inside other monorepo packages. But Lerna doesn’t update its version if it is in the root. In the example, @hela/cli is just one of the packages of this monorepo.

lerna.json

{
  "packages": [
    "packages/*"
  ],
  "useWorkspaces": true,
  "npmClient": "yarn",
  "version": "3.0.0-alpha.66",
  "command": {
    "version": {
      "message": "chore(release): version %s"
    }
  }
}

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.15.0
npm --version	6.9.0
yarn --version	1.16.0
node --version	10.x

OS	Version
NAME	VERSION
ArchLinux	none

[dcwarwick]

OK, I have hit the same (I think) issue with lerna. We have a jest config that we put into its own package in our monorepo as it is used by several different other packages, and we want to use the same jest config for our top-level test suite, so I added the jest config package as a dev dependency to the root package.json, but the next time lerna version bumped the version for the jest config package everything broke because it did not update the version in the root package.json.

Is there a particular reason that lerna does not update versions of packages if they are mentioned in the root package.json? If there isn’t, can this be quite easily fixed? And if there is, how should I be going about setting up some shared resources that are used both by one or more of the packages in my monorepo and by tools run at the root level?

[evocateur]

I would use a relative file: specifier in the root, and have your build run in a prestart lifecycle, with start pointing to the built output path.