Opt-out from the Terminal markdown rendered in dry-run mode

[n0th1ng-else]

New feature motivation

Hello. I wonder if we can opt-out from the Terminal markdown rendered when we run the semantic-release in --dry-run mode?

We use dry-run mode to render the upcoming release notes once developer opens a pull request. It actually does two things - first, it shows the expected version once the PR is merged into the main branch and secondly, it breaks the pipeline if the commit message was in the wrong format and semantic-release could not fetch the proper commit data. So it is kind of secures us from making mistakes while we specify the commit message.

The --dry-run mode transforms the release notes from the markdown into terminal-like text which is nice, looks a bit off in our case. When I put the result of the dry-run into the GitHub comment it looks not that nice.

So I wonder if we can introduce the flag that allows to output of the markdown release notes instead of getting it formatted with TerminalRendered? I understand using the markdown terminal formatted is for human readability, but I think we can find more examples of when the release notes can be useful in the raw markdown format

New feature description

Basically, I am thinking of an extra CLI flag that can be used in pair with --dry-run flag. Something, like npx semantic-release --dry-run --markdown-output would be enough I guess

New feature implementation

The idea is to introduce an additional flag (which is not a breaking change) and once we are in dry run mode, output the release notes with no changes here

[diogokiss]

Yes, I agree. The output is not being rendered properly when written in GitHub comments.