Lars Kappert

So there are a few options: * Add a `whatBump()` function to the options for this dependency, and parse the commits in this plugin (to add a return value of...

Totally agreed. Looks like `semantic-release` has a `analyzeCommits` step/plugin which parses commits itself (and potentially return `null`): https://github.com/semantic-release/commit-analyzer/blob/master/index.js

Looking into it again, I'm seeing basically all presets for recommended bump work the same. Here's the angular preset: https://github.com/conventional-changelog/conventional-changelog/blob/master/packages/conventional-changelog-angular/conventional-recommended-bump.js (this is the `whatBump` function). It always returns value `0`,...

> @webpro How does your example code snippet leverage `whatBump` to properly decide when to send `null` for the `level`? > > Are you suggesting that the function would be...

That would be nice, @jamesvillarrubia! Are you still up for this? Would be great to have options to ignore certain types of commits.

Maybe the function can be extended; I'll be happy to add it to the docs or maybe even merge it into the codebase (with some logic/option to enable it).

You can use `-VV` and/or `--debug` to see better what's going on.

I'm sorry, I meant `NODE_DEBUG=release-it:* release-it [...]` https://github.com/release-it/release-it?tab=readme-ov-file#troubleshooting--debugging

> Options are passed verbatim What I meant here was (only) the plugin options. The plugin options should be sent to the libs you mention. That might also shed light...

It doesn't, because I don't want to increase the API surface that much now.