How to prevent Lerna from automatically updating dependencies versions?

For example, say that I have 2 packages configured like this:

/packages/foo/package.json

{
  "name": "foo",
  "version": "1.0.0"
}

/packages/bar/package.json

{
  "name": "bar",
  "version": "1.0.0",
  "dependencies": {
    "foo": "1.0.0"
  }
}

I then make a breaking change to foo and on my next lerna publish three things will happen:

• foo version will be bumped to v2.0.0
• foo dependency in bar will also be bumped to v2.0.0
• bar version will be bumped to v1.0.1 (due to previous point)

Is there any way to prevent the automatic bump of the foo dependency in bar? And, consequentially, prevent the bar version bump to v1.0.1 (nothing changed after all).

[hendrikvolschenk]

package.json already indicates what it allows to install up to:

• >1.0.0 - Bump everything, including major.
• ~1.0.0 - Bump only patch versions.
• ^1.0.0 - Bump patch and minor versions.
• 1.0.0 - Don’t touch anything

If lerna could respect these when bumping other packages (while keeping/transferring the prefix) then it would work for many of us with the same needs as @rfgamaral and allow for even more control in other situations.

[BrianLoughnane]

+1 on this issue. Would love if sibling dep version ranges were respected (ie overwritten by a new range only if the new version matches the existing range). Seems that the current behavior is redundant to the “file:path/to/package” specifier but allows no such specification of sibling dep version ranges.