Draft the version the labels imply, not always a patch - #110
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The drafter numbered every release in this repo as a patch, because
$NEXT_PATCH_VERSIONignores theversion-resolver.
$RESOLVED_VERSIONreads it, so a PR labelledenhancementdrafts a minor.tag-prefixis the other half: without it the drafter parses the version out of the tag string as best itcan, which is how plexus-i18n came to draft
18.0.1— it read the 18 out of its own name.Depends on codehaus-plexus/.github#77, which makes the shared
name-templateresolve the same way.This change was created with AI assistance.