You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many CI solutions depend on bump commit messages having a predetermined format, such as bump: version 1.0.0 -> 1.0.1. The commit message for this plugin is simply the new version (i.e. "1.0.1"). Many other semantic-release solutions either already commit in the bump: format, and/or provide a method to override the default functionality.
Thanks for this very helpful plugin! I'd like to provide additional context to the great description given by @cvockrodt.
The commit message as it is actually does not match the conventional commit specification, which makes it incompatible with semantic release, and commit message verification tools such as Husky. Our CI crashes because of this hard-coded message:
[4:29:04 PM] [semantic-release] [@conveyal/maven-semantic-release] › ℹ committing changes
[4:29:05 PM] [semantic-release] › ✖ An error occurred while running semantic-release: Error: Command failed: git commit -m 0.1.2 [ci skip]
⧗ input: 0.1.2 [ci skip]
✖ subject may not be empty [subject-empty]
✖ type may not be empty [type-empty]
✖ found 2 problems, 0 warnings
ⓘ Get help: https://github.com/conventional-changelog/commitlint/#what-is-commitlint
Problem
Many CI solutions depend on bump commit messages having a predetermined format, such as bump: version 1.0.0 -> 1.0.1. The commit message for this plugin is simply the new version (i.e. "1.0.1"). Many other semantic-release solutions either already commit in the bump: format, and/or provide a method to override the default functionality.
Potential Solution
Add an additional command line flag such as --commit-message and utilize this option in https://github.com/conveyal/maven-semantic-release/blob/dev/lib/git.js#L103.
Defining Success
Default to or add the ability to override the commit message to a format such as "bump: version 1.0.0 -> 1.0.1"
The text was updated successfully, but these errors were encountered: