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
When using TagStrategy setPrefixNameWithV(false) the full contents of the Git history is contained in every release notes section. This is because the TagStrategy generateMessage closure grabs the "previousVersion" and always prefixes "v" in front of the commit that is looked up in the git repository (for which it never finds the commit since it's not there). The code of interest can be found here:
So, it appears the ReleasePlugin line 114 should simply be changed to: String previousVersion = "${project.release.tagStrategy.toTagString(version.previousVersion)}^{commit}"
sdavids13
added a commit
to sdavids13/nebula-release-plugin
that referenced
this issue
Apr 1, 2022
When using TagStrategy setPrefixNameWithV(false) the full contents of the Git history is contained in every release notes section. This is because the TagStrategy generateMessage closure grabs the "previousVersion" and always prefixes "v" in front of the commit that is looked up in the git repository (for which it never finds the commit since it's not there). The code of interest can be found here:
nebula-release-plugin/src/main/groovy/nebula/plugin/release/ReleasePlugin.groovy
Lines 113 to 122 in af18e2f
The text was updated successfully, but these errors were encountered: