Skip to content

Update dependency me.qoomon:maven-git-versioning-extension to v9.12.1 - #62

Merged
yawkat merged 1 commit into
mainfrom
renovate/me.qoomon-maven-git-versioning-extension-9.x
Aug 6, 2026
Merged

Update dependency me.qoomon:maven-git-versioning-extension to v9.12.1#62
yawkat merged 1 commit into
mainfrom
renovate/me.qoomon-maven-git-versioning-extension-9.x

Conversation

@renovate

@renovate renovate Bot commented Aug 6, 2026

Copy link
Copy Markdown

This PR contains the following updates:

Package Change Age Confidence
me.qoomon:maven-git-versioning-extension 9.11.09.12.1 age confidence

Release Notes

qoomon/maven-git-versioning-extension (me.qoomon:maven-git-versioning-extension)

v9.12.1: 9.12.1

What's Changed

New Contributors

Full Changelog: qoomon/maven-git-versioning-extension@v9.11.0...v9.12.1

v9.12.0

Features
  • 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 trailing
      digits of the label if a label is present (RC1RC2, RC10RC11); a label with no trailing
      digits is treated as having 0 at the end (alphaalpha1); otherwise bumps the rightmost
      numeric core component (build → patch → minor → major).
      • 1.2.3 → 1.2.4, 1.2.3.4 → 1.2.3.5
      • 1.2.3-RC1 → 1.2.3-RC2 (standard SemVer pre-release progression)
      • 1.2.3-alpha → 1.2.3-alpha1
      • RC1-final → RC1-final1 (only trailing digits — not RC2-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 calls
    Long.parseLong on the entire label and crashes on RC1.

Behavior changes
  • ${describe.tag.version} now includes the optional 4th .build segment when the matched tag has one.
    Previously, for a tag like 3.0.28.1, ${describe.tag.version} returned 3.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
  • The new version.build and version.next placeholders reserve the group names build and next inside
    <projectVersionPattern>. If you previously defined a capture group with either name there, the extension
    will now throw an IllegalArgumentException at startup ("project version pattern capture group can not be
    named '…', because this would overwrite extension placeholder ${version.…}"). Rename the group to resolve.
    (Named groups in <describeTagPattern> and <ref> patterns are unaffected — they use separate prefixes
    describe.tag. and ref. respectively, so a (?<build>…) or (?<next>…) there is still valid.)

Fixes #​412.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@yawkat
yawkat enabled auto-merge (squash) August 6, 2026 05:45
@yawkat
yawkat merged commit c93f15d into main Aug 6, 2026
6 checks passed
@yawkat
yawkat deleted the renovate/me.qoomon-maven-git-versioning-extension-9.x branch August 6, 2026 06:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant