[command:version] Version number in related peerDependencies don't update

When run lerna version also respect dependencies in peerDependencies.

Current Behavior

When execution lerna version the peerDependencies don’t update, but the devDependencies do. Here a result after the bumping version of packageA and packageB from 0.0.0 to 0.0.1

packageA

{
  "name": "packageA",
  "version": "0.0.1",
}

packageB

{
  "name": "packageB",
  "version": "0.0.1",
  "peerDependencies": {
    "@scope/packageA": "0.0.0"
  },
  "devDependencies": {
    "@scope/packageA": "0.0.1"
  }
}

Expected Behavior

packageA

{
  "name": "packageA",
  "version": "0.0.1",
}

packageB

{
  "name": "packageB",
  "version": "0.0.1",
  "peerDependencies": {
    "@scope/packageA": "0.0.1"
  },
  "devDependencies": {
    "@scope/packageA": "0.0.1"
  }
}

[arsnl]

@ValeryVS true. Peer dependencies don’t act the same as dev nor prod dependencies. However, in some case the peerDependencies should follow the current version. Maybe we should add a new option to the version command to cover this need? Something like --update-peer-dependencies.

[runspired]

An OSS project I work on with many packages in a mono-repo with peer-deps on each other moved to strictly declaring peerDependencies recently now that most package managers properly support and respect them. Unfortunately, this results in peerDependencies being incorrect. We can manually fix the versions during our release process; however, it makes lerna’s version command not all that useful since the commit and tag would not include this change.