sgrissom-mck commented on issue #1327: URL: https://github.com/apache/maven-scm/issues/1327#issuecomment-4283394447
I think I’m seeing a related issue here. I have a single merge request since tag 2.2.0. That merge has two parents: one line of history leads to the 2.2.0 tag, and the other leads back to a commit before 2.2.0. The release plugin is resolving the latest tag as 2.1.0, which breaks our release automation. At this point the only workaround I see is banning merge commits in the repo. This is coming from the conventional commits plugin usage of the ChangeLogSet API. It's attempting to find the latest tag, but what it gets back from the API is inaccurate. https://github.com/nielsbasjes/conventional-commits-maven-release/blob/main/src/main/java/nl/basjes/maven/release/version/conventionalcommits/CommitHistory.java#L93 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
