fix(warnings): all warnings should go to stdout
#1019
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
To be consistent with the build
warnings
module behavior and to avoid breaking the changelog when using--changelog-to-stdout
, all warnings generated withcommitizen.out.warn()
are printed tostderr
Checklist
./scripts/format
and./scripts/test
locally to ensure this change passes linter check and testExpected behavior
Whatever the warning raised during a
bump
or achangelog
command, they should be printed tostderr
.More especially, when you are trying to run one of the above command with
--changelog-to-stdout
and your repository have some tags not matching the tag pattern, changelog should not be mixed with repeatedInvalidVersion GitTag('not-a-version', 'sha1', 'yyyy-mm-dd')
statements.Steps to Test This Pull Request
Add a git tag not matching the
tag_format
to your repository.Run the
cz bump --changelog-to-stdout --git-output-to-stderr > CHANGELOG.md
command.CHANGELOG.md
should only contain the changelog.Same when using the
commitizen-action
, invalid tags should not appear in the changelog increment file.