With conventional commits, patch version is unexpectedly always increased

#1547 speaks more of this, but is closed.

Expected Behavior

• Have any package at version 1.0.0
• Make a change to this package and commit with chore: fix typo in readme
• Run lerna publish --yes as part of your CI
• Nothing is published, as a chore does not warrant a release

Current Behavior

• Have any package at version 1.0.0
• Make a change to this package and commit with chore: fix typo in readme
• Run lerna publish --yes as part of your CI
• Version 1.0.1 of package is published

Possible Solution

The version command should take an array of commit types to either whitelist of blacklist from affecting the bumping of a version.

Whitelist: only commits with these types can trigger a bump in version, other commits are completely ignored.

{
  "command": {
    "version": {
      "conventionalCommits": true,
      "conventionalWhitelist": [
        "feat",
        "fix"
      ],
      "message": "chore: release --skip-ci"
    }
  }
}

Blacklist: Commits with these types are completely ignored and cannot trigger a bump in version.

{
  "command": {
    "version": {
      "conventionalCommits": true,
      "conventionalBlacklist": [
        "chore"
      ],
      "message": "chore: release --skip-ci"
    }
  }
}

Steps to Reproduce (for bugs)

See expected and current behaviour section.

lerna.json

{
  "version": "independent",
  "npmClient": "yarn",
  "useWorkspaces": true,
  "packages": [
    "packages/*"
  ],
  "publishConfig": {
    "access": "restricted"
  },
  "command": {
    "version": {
      "allowBranch": "master",
      "conventionalCommits": true,
      "changelogPreset": "angular",
      "createRelease": "github",
      "commitHooks": "false",
      "message": "chore: release --skip-ci"
    }
  }
}

Context

We have a monorepo using Lerna to release and link a bunch of packages, but we also have Dependabot creating pull requests for dependency updates on a daily basis.

We like to stay up to date with our dependencies, as that is significantly easier than updating a dependency you haven’t updated in a year. But now every time we update aws-sdk (for example, a very active package), Lerna publishes a new patch version of all our packages using aws-sdk.

Now that’s annoying, but what happens next is that Dependabot creates pull requests for other repositories (both ours and for people all over the internet) with this amazing new release where the aws-sdk dependency has been updated.

This is creating a lot of noise for us, and likely for the users of our packages too.

Next to that, if I fix a typing error in a README, I really don’t see any reason to release a new version of the package for that. It’s completely useless.

Your Environment

Executable	Version
lerna --version	3.19.0
npm --version	6.12.1 (not used)
yarn --version	1.21.1
node --version	12.13.1

OS	Version
macOS Catalina	10.15.1
Ubuntu	18.04

[cmurczek-it]

As far as I can tell, it’s Lerna taking an opinionated (and IMHO very questionable) decision right here: https://github.com/lerna/lerna/blob/master/core/conventional-commits/lib/recommend-version.js#L54

Can anybody from the team share some insights or reasoning on why Lerna feels the need to override the versioning recommendation given by the configured preset?

[SleepWalker]

Looks like this behavior of meaningless releases will stay with lerna, because it’s not a bug but a feature 😅 . See #1569