Upgrade git-commit-id-maven-plugin 9.1.0 -> 10.0.0

[Picnic-DevPla-Bot]

This PR contains the following updates:

Package	Type	Update	Change
git-commit-id-maven-plugin	build	major	9.1.0 -> 10.0.0

---

Release Notes

git-commit-id/git-commit-id-maven-plugin (git-commit-id-maven-plugin)

v10.0.0: Version 10.0.0

Compare Source

Version 10.0.0 is finally there and includes various bug-fixes and improvements :-)

⚠️ This is a potentially breaking release. Read the release-notes carefully ⚠️

Potential Breaking changes:

The main key-aspects that might cause a breakage when migrating to the new version:

• #​913 / #​914: Require Maven 3.9.0 [Maven 3.6.3 is EOL] ⚠️

Getting the latest release

The plugin is available from Maven Central (see here), so you don't have to configure any additional repositories to use this plugin. All you need to do is to configure it inside your project as dependency:

<dependency>
    <groupId>io.github.git-commit-id</groupId>
    <artifactId>git-commit-id-maven-plugin</artifactId>
    <version>10.0.0</version>
</dependency>

Getting the latest snapshot (build automatically)

If you can't wait for the next release, you can also get the latest snapshot version from sonatype, that is being deployed automatically by github actions:

<pluginRepositories>
    <pluginRepository>
        <id>sonatype-snapshots</id>
        <name>Sonatype Snapshots</name>
         <url>https://s01.oss.sonatype.org/content/repositories/snapshots/</url>
    </pluginRepository>
</pluginRepositories>

Even though the github actions will only deploy a new snapshot once all tests have finished, it is recommended to rely on the released and more stable version.

Known Issues / Limitations:

• This plugin is unfortunately not working with Heroku which is due to the fact how Heroku works. In summary Heroku does not copy over the .git-repository but in order to determine the git properties this plugin relies on the fact that it has access to the git-repository. A somewhat workaround to get some information is outlined in ktoso/maven-git-commit-id-plugin#279 (comment)
• Using maven's plugin prefix resolution (e.g. mvn com.test.plugins:myPlugin:myMojo) might result in unresolved properties even with <injectAllReactorProjects>true</injectAllReactorProjects>. Please refer to git-commit-id/maven-git-commit-id-plugin#287 or git-commit-id/maven-git-commit-id-plugin#413 (comment) for details and potential workarounds

Reporting Problems

If you find any problem with this plugin, feel free to report it here

Full Changelog: git-commit-id/git-commit-id-maven-plugin@v9.2.0...v10.0.0

v9.2.0: Version 9.2.0

Compare Source

Version 9.2.0 is finally there and includes various bug-fixes and improvements :-)

New Features / Bug-Fixes:

The main key-aspects that have been improved or being worked on are the following:

• bump several plugins
  • bump io.github.git-commit-id:git-commit-id-plugin-core from 6.1.5 to 6.2.0
    • replace org.eclipse.jgit.ssh.jsch with org.eclipse.jgit:org.eclipse.jgit.ssh.apache (see https://github.com/eclipse-jgit/jgit/blob/master/org.eclipse.jgit.ssh.jsch/README.md)
    • add org.bouncycastle:bcpkix-jdk18on version 1.81
    • remove joda-time:joda-time [replaced with Java 8+ Time API]
    • replace com.google.code.findbugs:jsr305 version 3.0.2 with org.jspecify:jspecify version 1.0.0
    • Full list: https://github.com/git-commit-id/git-commit-id-plugin-core/releases/tag/v6.2.0

Getting the latest release

The plugin is available from Maven Central (see here), so you don't have to configure any additional repositories to use this plugin. All you need to do is to configure it inside your project as dependency:

<dependency>
    <groupId>io.github.git-commit-id</groupId>
    <artifactId>git-commit-id-maven-plugin</artifactId>
    <version>9.2.0</version>
</dependency>

Getting the latest snapshot (build automatically)

If you can't wait for the next release, you can also get the latest snapshot version from sonatype, that is being deployed automatically by github actions:

<pluginRepositories>
    <pluginRepository>
        <id>sonatype-snapshots</id>
        <name>Sonatype Snapshots</name>
         <url>https://s01.oss.sonatype.org/content/repositories/snapshots/</url>
    </pluginRepository>
</pluginRepositories>

Even though the github actions will only deploy a new snapshot once all tests have finished, it is recommended to rely on the released and more stable version.

Known Issues / Limitations:

• This plugin is unfortunately not working with Heroku which is due to the fact how Heroku works. In summary Heroku does not copy over the .git-repository but in order to determine the git properties this plugin relies on the fact that it has access to the git-repository. A somewhat workaround to get some information is outlined in ktoso/maven-git-commit-id-plugin#279 (comment)
• Using maven's plugin prefix resolution (e.g. mvn com.test.plugins:myPlugin:myMojo) might result in unresolved properties even with <injectAllReactorProjects>true</injectAllReactorProjects>. Please refer to git-commit-id/maven-git-commit-id-plugin#287 or git-commit-id/maven-git-commit-id-plugin#413 (comment) for details and potential workarounds

Reporting Problems

If you find any problem with this plugin, feel free to report it here

Full Changelog: git-commit-id/git-commit-id-maven-plugin@v9.1.0...v9.2.0

---

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

[github-actions]

Suggested commit message:

Upgrade git-commit-id-maven-plugin 9.1.0 -> 10.0.0 (#2190)

See:
- https://github.com/git-commit-id/git-commit-id-maven-plugin/releases/tag/v9.2.0
- https://github.com/git-commit-id/git-commit-id-maven-plugin/releases/tag/v10.0.0
- https://github.com/git-commit-id/git-commit-id-maven-plugin/compare/v9.1.0...v10.0.0

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: f3334c3b-3b9c-404e-83ca-43c1c9ad6e4a

📥 Commits

Reviewing files that changed from the base of the PR and between 1afa509 and 14f013d.

📒 Files selected for processing (1)

• pom.xml

---

📝 Walkthrough

Walkthrough

Updated git-commit-id-maven-plugin version from 9.1.0 to 10.0.0 in the project dependencies. No configuration changes or functional alterations are included in this update.

Changes

Cohort / File(s)	Summary
Dependency Version Update pom.xml	Bumped io.github.git-commit-id:git-commit-id-maven-plugin from version 9.1.0 to 10.0.0; all plugin configuration remains unchanged.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• Upgrade git-commit-id-maven-plugin 9.0.2 -> 9.1.0 #2180: Earlier version bump of the same git-commit-id-maven-plugin from 9.0.2 to 9.1.0; this PR continues the version progression to 10.0.0.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title directly and clearly summarizes the main change: upgrading a Maven plugin from version 9.1.0 to 10.0.0.
Description check	✅ Passed	The description is comprehensive and directly related to the changeset, providing release notes, breaking change information, and version details for the upgraded plugin.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch renovate/git-commit-id-maven-plugin-10.x

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

[github-actions]

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

[github-actions]

Looks good. No mutations were possible for these changes.
Mutation testing report by Pitest. Review any surviving mutants by inspecting the line comments under Files changed.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud