If you would consider this change too much, less obtrusive variant would be replace it only for warn (and possibly info), and leave log method outputting to stdout.

Open in Stackblitz

npm i https://pkg.pr.new/release-it@1207

commit: f897fdb

Don't use console.log for logging, as it outputs to stdout instead of stderr.

I guess it depends on exactly what output we're talking about. Not ALL logging must go to stderr. What specifically is problematic or incorrect?

When used from scripts, it is impossible to use e. g. release-it --release-version --increment major with conventional-changelog, because that outputs

VERSION=WARNING The recommended bump is "minor", but is overridden with "major".
1.0.0

instead of two streams, and version only in stdout.

I would agree that the first line with the warning should not go to stdout, if that's what you mean?

I've checked that --release-version and --changelog arguments already use (correctly) console.log directly, and I've replaced log for cli commands.

There's a separate --ci mode which is automatically enabled in CI environments.

The default mode will ask feedback from the user and print changelog, etc. - this could go to stdout just fine I'd say.

If you would consider this change too much, less obtrusive variant would be replace it only for warn (and possibly info), and leave log method outputting to stdout.

It's a bit much indeed, but the good thing is that your timing is great as we're heading towards a new v19 which could introduce potentially breaking changes like this. Please consider this my initial review, I'll give it a closer look when I can.

OK, so proposed variant would be:

Log warnings and info to stderr, but log() method should still print to stdout, to follow console own behavior. I'll verify usage in the code.

This should work fine in CI, since commands that are useful in shell scripts should not use log(), even in nested code (I'll also verify this).

Sounds like a plan to me! 👍 I won't have time today to review or work on things, but certainly within a few days.

Pushed updated version, plus I've added process.exit(1) for --release-version and --changelog, if the command failed. Otherwise it prints either empty string, or worse, "undefined".

Fixed conflicts after merging another branch to main.

Thanks, Michal! Much appreciated.

🚀 This pull request is included in v19.0.0-next.2. See Release 19.0.0-next.2 for release notes.