Do not publish new version of a package if only change is dependency version which follows semver range

[trivikr]

Is your feature request related to a problem? Please describe.
A new version of a package is published even if the only change is dependency update which follows semver range:

Example releases for @aws-sdk/abort-controller where only changes are dependencies:

• v1.0.0-alpha.2
  • The only change is dependency update from @aws-sdk/types@^1.0.0-alpha.2 to @aws-sdk/types@^1.0.0-alpha.3
• v1.0.0-alpha.3
  • The only change is dependency update from @aws-sdk/types@^1.0.0-alpha.3 to @aws-sdk/types@^1.0.0-alpha.4
• v1.0.0-alpha.4
  • The only change is dependency update from @aws-sdk/types@^1.0.0-alpha.4 to @aws-sdk/types@^1.0.0-alpha.5

Describe the solution you'd like

• [Preferred to minimize dependency updates] Do not update package dependency version, if the new version follows semver range
• [Backup] Do not publish a new version of package, if the only change is update in dependency version which follows semver range

Describe alternatives you've considered
Continue to publish new versions, and manage those every increasing version numbers

[trivikr]

This issue was fixed after moving to lerna fixed versioning in #1577

[github-actions]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs and link to relevant comments in this thread.