dependabot[bot] opened a new pull request, #169:
URL: https://github.com/apache/commons-dbutils/pull/169

   Bumps 
[spotbugs-maven-plugin](https://github.com/spotbugs/spotbugs-maven-plugin) from 
4.4.2 to 4.7.3.0.
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a 
href="https://github.com/spotbugs/spotbugs-maven-plugin/releases";>spotbugs-maven-plugin's
 releases</a>.</em></p>
   <blockquote>
   <h2>Spotbugs Maven Plugin 4.7.3.0</h2>
   <ul>
   <li>Supports spotbugs 4.7.3</li>
   <li>note: 4.7.2.2 was released and actually included 4.7.3 by default.  All 
items in 4.7.2.2 are in this release with only change being to denote 
underlying spotbugs.</li>
   </ul>
   <h2>Spotbugs Maven Plugin 4.7.2.2</h2>
   <ul>
   <li>Groovy bumped to 4.0.6</li>
   <li>Make sarifOutputDirectory and sarifOutputFilename configurable per <a 
href="https://github-redirect.dependabot.com/spotbugs/spotbugs-maven-plugin/issues/506";>#506</a>
 and <a 
href="https://github-redirect.dependabot.com/spotbugs/spotbugs-maven-plugin/issues/507";>#507</a></li>
   </ul>
   <p>notice: This is actually running spotbugs 4.7.3.  A new release will be 
pushed that directly shows that.  Sorry for any confusion.</p>
   <h2>Spotbugs Maven Plugin 4.7.2.1</h2>
   <ul>
   <li>Bumps groovy to 4.0.5</li>
   <li>Bumps asm to 9.4</li>
   </ul>
   <p>Build Related</p>
   <ul>
   <li>For reproducible builds, timestamp is now more accurate to the 
release.</li>
   </ul>
   <h2>Spotbugs Maven Plugin 4.7.2.0</h2>
   <ul>
   <li>support for spotbugs 4.7.2</li>
   </ul>
   <h2>Spotbugs Maven Plugin 4.7.1.1</h2>
   <p>Patch Release</p>
   <ul>
   <li>Validate Spotbugs report even if only test sources exist fixing <a 
href="https://github-redirect.dependabot.com/spotbugs/spotbugs-maven-plugin/issues/454";>#454</a></li>
   <li>Moved javaparser-core to project level to resolve issues with site 
releases</li>
   <li>Code cleanup throughout</li>
   <li>General build updates</li>
   <li>Fixed l10n on site documentation</li>
   </ul>
   <h2>Spotbugs Maven Plugin 4.7.1.0</h2>
   <ul>
   <li>Support spotbugs 4.7.1</li>
   <li>Add support for multiple bug inclusion, excusion, and baseline files.  
See PR <a 
href="https://github-redirect.dependabot.com/spotbugs/spotbugs-maven-plugin/issues/436";>#436</a></li>
   <li>Build Updates including usage of asm bom, groovy bom, and adjustment to 
asm to ensure it works after maven changes</li>
   <li>Invoker plugin set to groovy 3 while project is groovy 4 as invoker 
needs older groovy.</li>
   </ul>
   <h2>Spotbugs-maven-plugin 4.7.0.0</h2>
   <ul>
   <li>Support spotbugs 4.7.0</li>
   <li>Fix <a 
href="https://github-redirect.dependabot.com/spotbugs/spotbugs-maven-plugin/issues/68";>#68</a>,
 note still requires use of a separate plugin, see 
[here}(https://github.com/spotbugs/spotbugs-maven-plugin#eclipse-m2e-integration)</li>
   <li>Fix <a 
href="https://github-redirect.dependabot.com/spotbugs/spotbugs-maven-plugin/issues/114";>#114</a>
 by introducing verify mojo to allow split of analysis and verification into 
lifecycle phases of one's choosing.  One use case for that is running multiple 
code analyzers at once and only failing the build at a later stage, so that all 
of them have a chance to run.  Verify then in this case just uses an existing 
file.</li>
   <li>Updated readme with various information about groovy, security manager, 
and m2e specific to this application considerations that are often asked 
about.</li>
   </ul>
   <h2>Spotbugs-maven-plugin 4.6.0.0</h2>
   <ul>
   <li>Spotbugs 4.6.0 support</li>
   <li>Groovy 4.0.1 based</li>
   </ul>
   <p>note on groovy: If using groovy with same group id (already existing 
condition), an error may occur if not on same version.  To alleviate that, make 
sure groovy artifacts are defined in dependency management in order to force 
the loaded version correctly on your usage.</p>
   <p>note on 4.6.0.1/4.6.0.2: no change, not released.  Issue with site 
distribution via maven release plugin only that is being tested, use 4.6.0.0 
only.</p>
   <h2>Spotbugs-maven-plugin 4.5.3.0</h2>
   <ul>
   <li>Support spotbugs maven plugin 4.5.3.0</li>
   </ul>
   <!-- raw HTML omitted -->
   </blockquote>
   <p>... (truncated)</p>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/spotbugs/spotbugs-maven-plugin/commit/a084687f6bb4706314cc57c0119a79135ba053f6";><code>a084687</code></a>
 [maven-release-plugin] prepare release spotbugs-maven-plugin-4.7.3.0</li>
   <li><a 
href="https://github.com/spotbugs/spotbugs-maven-plugin/commit/99061cb2526a26536b767a2305198084942524b7";><code>99061cb</code></a>
 Merge pull request <a 
href="https://github-redirect.dependabot.com/spotbugs/spotbugs-maven-plugin/issues/509";>#509</a>
 from hazendaz/spotbugs</li>
   <li><a 
href="https://github.com/spotbugs/spotbugs-maven-plugin/commit/371096c3b2dd6f320006b9d9fd95c411e93d48fc";><code>371096c</code></a>
 [pom] Set rest of spotbugs 4.7.3 artifacts</li>
   <li><a 
href="https://github.com/spotbugs/spotbugs-maven-plugin/commit/d46ad44ad6c0b1782f2dfce57a59436e27e4ee79";><code>d46ad44</code></a>
 [maven-release-plugin] prepare for next development iteration</li>
   <li><a 
href="https://github.com/spotbugs/spotbugs-maven-plugin/commit/f8450ddacc7328075693c6e56d3cdb2844767d1c";><code>f8450dd</code></a>
 [maven-release-plugin] prepare release spotbugs-maven-plugin-4.7.2.2</li>
   <li><a 
href="https://github.com/spotbugs/spotbugs-maven-plugin/commit/24a8bb294680413a781efdbf73735b763830860c";><code>24a8bb2</code></a>
 Merge pull request <a 
href="https://github-redirect.dependabot.com/spotbugs/spotbugs-maven-plugin/issues/508";>#508</a>
 from jwgmeligmeyling/issues/506-507</li>
   <li><a 
href="https://github.com/spotbugs/spotbugs-maven-plugin/commit/e148e19538bccf78a215e95f520274a7a249839b";><code>e148e19</code></a>
 Make sarifOutputDirectory and sarifOutputFilename configurable</li>
   <li><a 
href="https://github.com/spotbugs/spotbugs-maven-plugin/commit/f01a7f6b99da3d2e6dcdbddd20f0b4e4dfac73fa";><code>f01a7f6</code></a>
 Merge pull request <a 
href="https://github-redirect.dependabot.com/spotbugs/spotbugs-maven-plugin/issues/504";>#504</a>
 from spotbugs/renovate/versionspluginversion</li>
   <li><a 
href="https://github.com/spotbugs/spotbugs-maven-plugin/commit/717ab1ec1f3aec7a5131a4c561942756b456c09a";><code>717ab1e</code></a>
 Merge pull request <a 
href="https://github-redirect.dependabot.com/spotbugs/spotbugs-maven-plugin/issues/503";>#503</a>
 from spotbugs/renovate/plexusutilsversion</li>
   <li><a 
href="https://github.com/spotbugs/spotbugs-maven-plugin/commit/a01ef40e5a6ffd2deff1f125b717396b671f1536";><code>a01ef40</code></a>
 Update dependency org.codehaus.mojo:versions-maven-plugin to v2.13.0</li>
   <li>Additional commits viewable in <a 
href="https://github.com/spotbugs/spotbugs-maven-plugin/compare/spotbugs-maven-plugin-4.4.2...spotbugs-maven-plugin-4.7.3.0";>compare
 view</a></li>
   </ul>
   </details>
   <br />
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=com.github.spotbugs:spotbugs-maven-plugin&package-manager=maven&previous-version=4.4.2&new-version=4.7.3.0)](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 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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to