fix: use rprint instead of click.echo for Rich markup error messages by frankgoldfish · Pull Request #1437 · python-semantic-release/python-semantic-release

@frankgoldfish

When `semantic-release version` is run with `--strict` and no new
commits have been found, the error message containing Rich markup
([bold orange1]...) was passed to `click.echo()` instead of
`rprint()`, causing the markup tags to be printed literally rather
than rendered as formatted text.

The non-strict path correctly used `rprint()`. This commit makes the
strict path consistent by also using `rprint(file=sys.stderr)` to
render the markup before writing to stderr.

Fixes python-semantic-release#1423