conventional-changelog/standard-version

Lifecycle Message Corrupts Commit Message

cutterbl opened this issue · 1 comments

I have a precommit lifecycle script that generates a file and does a git add. My npm release script uses the -a flag to make sure that file is included in the tag. I notice that now the tag commit message is outputting the content of my lifecycle script, instead of the standard message format for the tag. What am I doing wrong here?

If your lifecycle script prints anything, it is used as the message. You can fix this by not printing anything during your lifecycle script.