dependabot[bot] opened a new pull request, #9:
URL: https://github.com/apache/maven-rar-plugin/pull/9

   Bumps 
[org.apache.maven.plugins:maven-plugins](https://github.com/apache/maven-parent)
 from 36 to 41.
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a 
href="https://github.com/apache/maven-parent/releases";>org.apache.maven.plugins:maven-plugins's
 releases</a>.</em></p>
   <blockquote>
   <h2>41</h2>
   <h2>Improvement</h2>
   <ul>
   <li>[<a href="https://issues.apache.org/jira/browse/MPOM-426";>MPOM-426</a>] 
- downgrade plexus-xml to 3.0.0: 4.0.0 is incompatible with Maven 3</li>
   <li>[<a href="https://issues.apache.org/jira/browse/MPOM-429";>MPOM-429</a>] 
- Support development with Java 21 (palantirJavaFormat)</li>
   <li>[<a href="https://issues.apache.org/jira/browse/MPOM-443";>MPOM-443</a>] 
- Skip empty surefire reports</li>
   </ul>
   <h2>Task</h2>
   <ul>
   <li>[<a href="https://issues.apache.org/jira/browse/MPOM-427";>MPOM-427</a>] 
- use version.artifactId property for dependency versions (like plugins)</li>
   <li>[<a href="https://issues.apache.org/jira/browse/MPOM-436";>MPOM-436</a>] 
- Remove quality-checks profile with maven-docck-plugin</li>
   <li>[<a href="https://issues.apache.org/jira/browse/MPOM-445";>MPOM-445</a>] 
- Use maven-checkstyle-plugin version from parent</li>
   </ul>
   <h2>Dependency upgrade</h2>
   <ul>
   <li>[<a href="https://issues.apache.org/jira/browse/MPOM-425";>MPOM-425</a>] 
- Bump com.diffplug.spotless:spotless-maven-plugin from 2.37.0 to 2.40.0</li>
   <li>[<a href="https://issues.apache.org/jira/browse/MPOM-441";>MPOM-441</a>] 
- Bump maven-jxr-plugin from 3.3.0 to 3.3.1</li>
   <li>[<a href="https://issues.apache.org/jira/browse/MPOM-442";>MPOM-442</a>] 
- Bump org.cyclonedx:cyclonedx-maven-plugin from 2.7.9 to 2.7.10</li>
   <li>[<a href="https://issues.apache.org/jira/browse/MPOM-444";>MPOM-444</a>] 
- Bump maven-pmd-plugin from 3.21.0 to 3.21.2</li>
   <li>[<a href="https://issues.apache.org/jira/browse/MPOM-446";>MPOM-446</a>] 
- Upgrade Parent to 31</li>
   </ul>
   <h2>40</h2>
   <h2>New Feature</h2>
   <ul>
   <li>[<a href="https://issues.apache.org/jira/browse/MPOM-346";>MPOM-346</a>] 
- publish SBOM on release</li>
   </ul>
   <h2>Improvement</h2>
   <ul>
   <li>[<a href="https://issues.apache.org/jira/browse/MPOM-397";>MPOM-397</a>] 
- Don not run ITs during release</li>
   <li>[<a href="https://issues.apache.org/jira/browse/MPOM-422";>MPOM-422</a>] 
- Bump modello from 2.1.1 to 2.1.2</li>
   </ul>
   <h2>Task</h2>
   <ul>
   <li>[<a href="https://issues.apache.org/jira/browse/MPOM-200";>MPOM-200</a>] 
- remove Apache Resource Bundles parent POM</li>
   <li>[<a href="https://issues.apache.org/jira/browse/MPOM-415";>MPOM-415</a>] 
- Use surefire/failsafe version from ASF parent</li>
   </ul>
   <h2>Dependency upgrade</h2>
   <ul>
   <li>[<a href="https://issues.apache.org/jira/browse/MPOM-390";>MPOM-390</a>] 
- Upgrade to Maven Fluido Skin 1.11.2</li>
   <li>[<a href="https://issues.apache.org/jira/browse/MPOM-391";>MPOM-391</a>] 
- Upgrade to Maven Surefire 3.0.0-M8</li>
   <li>[<a href="https://issues.apache.org/jira/browse/MPOM-392";>MPOM-392</a>] 
- Upgrade to Maven Checkstyle Plugin 3.2.1</li>
   <li>[<a href="https://issues.apache.org/jira/browse/MPOM-393";>MPOM-393</a>] 
- Upgrade to Maven PMD Plugin 3.21.0</li>
   <li>[<a href="https://issues.apache.org/jira/browse/MPOM-412";>MPOM-412</a>] 
- Bump maven-enforcer-plugin to 3.3.0 and extra-enforcer-rules from 1.6.1 to 
1.7.0</li>
   </ul>
   <!-- raw HTML omitted -->
   </blockquote>
   <p>... (truncated)</p>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li>See full diff in <a 
href="https://github.com/apache/maven-parent/commits";>compare view</a></li>
   </ul>
   </details>
   <br />
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=org.apache.maven.plugins:maven-plugins&package-manager=maven&previous-version=36&new-version=41)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   Dependabot will resolve any conflicts with this PR as long as you don't 
alter it yourself. You can also trigger a rebase manually by commenting 
`@dependabot rebase`.
   
   [//]: # (dependabot-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   <details>
   <summary>Dependabot commands and options</summary>
   <br />
   
   You can trigger Dependabot actions by commenting on this PR:
   - `@dependabot rebase` will rebase this PR
   - `@dependabot recreate` will recreate this PR, overwriting any edits that 
have been made to it
   - `@dependabot merge` will merge this PR after your CI passes on it
   - `@dependabot squash and merge` will squash and merge this PR after your CI 
passes on it
   - `@dependabot cancel merge` will cancel a previously requested merge and 
block automerging
   - `@dependabot reopen` will reopen this PR if it is closed
   - `@dependabot close` will close this PR and stop Dependabot recreating it. 
You can achieve the same result by closing it manually
   - `@dependabot show <dependency name> ignore conditions` will show all of 
the ignore conditions of the specified dependency
   - `@dependabot ignore this major version` will close this PR and stop 
Dependabot creating any more for this major version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this minor version` will close this PR and stop 
Dependabot creating any more for this minor version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this dependency` will close this PR and stop 
Dependabot creating any more for this dependency (unless you reopen the PR or 
upgrade to it yourself)
   
   
   </details>


-- 
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: issues-unsubscr...@maven.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to