dependabot[bot] opened a new pull request, #27972:
URL: https://github.com/apache/camel/pull/27972

   Bumps 
[io.github.classgraph:classgraph](https://github.com/classgraph/classgraph) 
from 4.8.198 to 4.8.199.
   <details>
   <summary>Release notes</summary>
   <p><em>Sourced from <a 
href="https://github.com/classgraph/classgraph/releases";>io.github.classgraph:classgraph's
 releases</a>.</em></p>
   <blockquote>
   <h2>ClassGraph 4.8.199</h2>
   <p><strong>4.8.199 is the last ClassGraph 4.x release.</strong> ClassGraph 
4.x has reached end of life: there will be no further 4.x releases, other than 
releases that backport fixes for serious bugs.</p>
   <p><strong>Please upgrade to <a 
href="https://github.com/classgraph/classgraph/releases/tag/classgraph-6.0.0";>ClassGraph
 6</a></strong>, the new mainline release, for JDK 25 and newer. If your 
project must still run on JDK 17 to 24, use <strong><a 
href="https://github.com/classgraph/classgraph/releases/tag/classgraph-5.0.0";>ClassGraph
 5</a></strong> until it can move to JDK 25. ClassGraph 5 has the same API and 
behavior as ClassGraph 6, and will be kept in sync with it for the near future. 
Both have a new API: the <strong><a 
href="https://github.com/classgraph/classgraph/wiki/Porting-ClassGraph-4.x-code-to-ClassGraph-6.x";>porting
 guide</a></strong> walks through the port from 4.x step by step, and a coding 
agent can follow it for you.</p>
   <h2>Bug fixes</h2>
   <ul>
   <li><strong>A long chain of jarfiles that refer to each other through 
<code>Class-Path</code> manifest entries no longer overflows the 
stack.</strong> The classpath order was computed by recursing once per jarfile 
in the chain, so a long enough chain made the scan fail with 
<code>StackOverflowError</code>, sooner on a thread with a small stack. The 
order is now computed without recursion, and is the same as before.</li>
   </ul>
   <h2>Other changes</h2>
   <p>Unused imports were removed and imports sorted, and a test that could 
fail on Windows when its HTTP server refused a connection was fixed. The public 
API is unchanged from 4.8.198, and the release is still built for JDK 8.</p>
   </blockquote>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/classgraph/classgraph/commit/82d83a1cbba6919457bcc19d716f228d54b6c6e0";><code>82d83a1</code></a>
 [maven-release-plugin] prepare release classgraph-4.8.199</li>
   <li><a 
href="https://github.com/classgraph/classgraph/commit/072d38984d9ec8d2a8fc76f6c61d02d373a41b97";><code>072d389</code></a>
 Give the redirect test's HTTP server a backlog of 50</li>
   <li><a 
href="https://github.com/classgraph/classgraph/commit/6d2d831545e415ec55f3dc806bf93535ebee2d45";><code>6d2d831</code></a>
 Remove unused imports, and sort imports in the same grouping as main</li>
   <li><a 
href="https://github.com/classgraph/classgraph/commit/d6db33f4066395e6a48c09553b72b5b027a5d021";><code>d6db33f</code></a>
 Swallow errors from reflection driver setup again (revert R16 backport)</li>
   <li><a 
href="https://github.com/classgraph/classgraph/commit/099aa255de5a78fed38ca43729a127cffb270302";><code>099aa25</code></a>
 Avoid stack overflow in manifest dependency ordering (R05)</li>
   <li><a 
href="https://github.com/classgraph/classgraph/commit/0b3ca7d838f4646048ea5f0da8b6aac786877f97";><code>0b3ca7d</code></a>
 Propagate fatal reflection bootstrap errors (R16 backport)</li>
   <li><a 
href="https://github.com/classgraph/classgraph/commit/7c5b873928be8e5a21e0f1db65f7125d7d481071";><code>7c5b873</code></a>
 [maven-release-plugin] prepare for next development iteration</li>
   <li>See full diff in <a 
href="https://github.com/classgraph/classgraph/compare/classgraph-4.8.198...classgraph-4.8.199";>compare
 view</a></li>
   </ul>
   </details>
   <br />
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=io.github.classgraph:classgraph&package-manager=maven&previous-version=4.8.198&new-version=4.8.199)](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 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: [email protected]

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

Reply via email to