WhatBump returning undefined skips release

[Blackclaws]

This pull request adds support for whatBump returning undefined leading to no release being made.

[pkg-pr-new]

Open in Stackblitz

yarn add https://pkg.pr.new/@release-it/[email protected]

commit: ff1f342

[oluwatobiss]

Although this PR is a handy option for running release-it without releasing any version, it does not resolve instances where a version release is necessary. It will also require using a non-JSON config file to support passing a function to whatBump. Otherwise, #101's ERROR whatBump is not a function error will persist.

Why don't we pass a function directly into await bumper.bump() and allow the releaseType to accept undefined or the bump version (patch, minor, or major). So something like this:

const bumpVersion = 'patch'; // I've yet to figure out how to get the bump version.
const result = await bumper.bump(async () => {
   return { releaseType: options.whatBump == 'undefined' ? undefined : bumpVersion }
});

By so doing, we can use any config file since options.whatBump no longer needs to be a function. Here's a JSON example:

{
  "plugins": {
    "@release-it/conventional-changelog": {
      "preset": "conventionalcommits",
      "whatBump": "undefined"
    }
  }
}

[webpro]

@Blackclaws Thanks! Will release shortly.

@oluwatobiss Feel free to open a ticket or PR and we can take it from there.