Update dependency me.qoomon:maven-git-versioning-extension to v9.12.1 - #62
Merged
yawkat merged 1 commit intoAug 6, 2026
Merged
Conversation
yawkat
enabled auto-merge (squash)
August 6, 2026 05:45
yawkat
deleted the
renovate/me.qoomon-maven-git-versioning-extension-9.x
branch
August 6, 2026 06:07
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
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.
This PR contains the following updates:
9.11.0→9.12.1Release Notes
qoomon/maven-git-versioning-extension (me.qoomon:maven-git-versioning-extension)
v9.12.1: 9.12.1What's Changed
New Contributors
Full Changelog: qoomon/maven-git-versioning-extension@v9.11.0...v9.12.1
v9.12.0Features
Support 4-segment tag versions (e.g.
3.0.28.1). New placeholders:${describe.tag.version.build},${describe.tag.version.build.next}${describe.tag.version.build.plus.describe.distance},${describe.tag.version.build.next.plus.describe.distance}${version.build},${version.build.next}Shape-aware version-increment placeholders that pick the right segment based on the parsed version's shape:
${describe.tag.version.next}— one numeric segment of the tag bumped by 1. Bumps the trailingdigits of the label if a label is present (
RC1→RC2,RC10→RC11); a label with no trailingdigits is treated as having
0at the end (alpha→alpha1); otherwise bumps the rightmostnumeric core component (build → patch → minor → major).
1.2.3 → 1.2.4,1.2.3.4 → 1.2.3.51.2.3-RC1 → 1.2.3-RC2(standard SemVer pre-release progression)1.2.3-alpha → 1.2.3-alpha1RC1-final → RC1-final1(only trailing digits — notRC2-final).${version.next}— same semantics applied to the project's<version>.Note: this is strictly more capable than
${...label.next}for RC-style labels — the latter callsLong.parseLongon the entire label and crashes onRC1.Behavior changes
${describe.tag.version}now includes the optional 4th.buildsegment when the matched tag has one.Previously, for a tag like
3.0.28.1,${describe.tag.version}returned3.0.28(silently dropping the 4th segment).After this change it returns
3.0.28.1. 3-segment tags are unaffected.${version}itself is unchanged — it returns the raw project<version>and never went through the regex.Migration
version.buildandversion.nextplaceholders reserve the group namesbuildandnextinside<projectVersionPattern>. If you previously defined a capture group with either name there, the extensionwill now throw an
IllegalArgumentExceptionat startup ("project version pattern capture group can not benamed '…', because this would overwrite extension placeholder ${version.…}"). Rename the group to resolve.
(Named groups in
<describeTagPattern>and<ref>patterns are unaffected — they use separate prefixesdescribe.tag.andref.respectively, so a(?<build>…)or(?<next>…)there is still valid.)Fixes #412.
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.