I also tried:

commit_message = "{version}\n\nVersion generated by python-semantic-release [[ci skip]]"

with no luck:

[🛡 NOP]         would have run:
                            GIT_AUTHOR_NAME=semantic-release \
    GIT_AUTHOR_EMAIL=semantic-release \
    GIT_COMMITTER_NAME=semantic-release \
    GIT_COMMITTER_EMAIL=semantic-release \
    git commit -m '6.237.5

            Version generated by python-semantic-release []'

Have you actually tried running the project not in --noop mode? The log is likely misinterpreted by the terminal as an ansi escape code.

If you don't want all the steps to execute and it easily revertable then use:

semantic-release version --no-tag --no-push --skip-build

Have you actually tried running the project not in --noop mode? The log is likely misinterpreted by the terminal as an ansi escape code.

If you don't want all the steps to execute and it easily revertable then use:

semantic-release version --no-tag --no-push --skip-build

you are right, it actually works as expected, thanks!

Author: semantic-release <semantic-release>
Date:   Fri May 23 16:12:22 2025 +0200

    6.237.5
    
    Version generated by python-semantic-release [ci skip]

should we still keep the issue open so the --noop mode is fixed to be consistent with the real one?

There is probably nothing I can do since I don't do any processing on that output. It's using the rich console formatter on top of the logging mechanism. I can look around for an escape function and apply it to that one log line as it's not intended to have colors. But I might just close it if that doesn't exist.