dependabot[bot] opened a new pull request, #24038: URL: https://github.com/apache/camel/pull/24038
Bumps [eu.maveniverse.maven.scalpel:extension3](https://github.com/maveniverse/scalpel) from 0.3.3 to 0.3.4. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/maveniverse/scalpel/releases";>eu.maveniverse.maven.scalpel:extension3's releases</a>.</em></p> <blockquote> <h2>Scalpel 0.3.4</h2> <p>Compute transitively affected modules when no modules are directly affected (<a href="https://redirect.github.com/maveniverse/scalpel/issues/33";>#33</a>)</p> <p>When a BOM property change affects managed dependencies but no module is directly affected (e.g. the property is only used in dependencyManagement), computeTransitivelyAffected was never called because the code returned early. This caused report mode to produce an empty affectedModules list, and trim/skip-tests modes to treat the build as unaffected.</p> <p>This has been quite problematic for the Quarkus project as a change to our BOM doesn't properly trigger a build of the affected modules. We have a safeguard and we trigger the full build when no modules are affected but this is far from ideal.</p> <p>If this makes sense, I would appreciate a quick release, thanks!</p> <p>Assisted-By: Claude Opus 4.6 <a href="mailto:[email protected]";>[email protected]</a></p> <!-- raw HTML omitted --> <h2>Summary by CodeRabbit</h2> <ul> <li> <p><strong>Bug Fixes</strong></p> <ul> <li>Improved detection of modules affected by managed dependency and plugin version changes.</li> <li>Fixed build set computation to properly include transitively affected modules in skip-tests and trim modes.</li> </ul> </li> <li> <p><strong>Tests</strong></p> <ul> <li>Added test coverage for BOM property version change scenarios with transitive dependencies.</li> </ul> </li> </ul> <!-- raw HTML omitted --> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/maveniverse/scalpel/commit/91ef9f6da85baab1f8beb804b7f409b1f4f8ea8b";><code>91ef9f6</code></a> Compute transitively affected modules when no modules are directly affected (...</li> <li><a href="https://github.com/maveniverse/scalpel/commit/a5c493deba2cb696e30b67f6cc32aaacf3e489e3";><code>a5c493d</code></a> Parent POM 55 (<a href="https://redirect.github.com/maveniverse/scalpel/issues/32";>#32</a>)</li> <li><a href="https://github.com/maveniverse/scalpel/commit/1cf42659ebc58cf30839f80b68eaf1c40a928052";><code>1cf4265</code></a> Document TRANSITIVE category in README report tables</li> <li>See full diff in <a href="https://github.com/maveniverse/scalpel/compare/0.3.3...0.3.4";>compare view</a></li> </ul> </details> <br /> [](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]
