chore(deps)(deps): bump org.owasp.dependencycheck from 12.2.2 to 13.0.0 - #228
chore(deps)(deps): bump org.owasp.dependencycheck from 12.2.2 to 13.0.0#228dependabot[bot] wants to merge 1 commit into
Conversation
Bumps org.owasp.dependencycheck from 12.2.2 to 13.0.0. --- updated-dependencies: - dependency-name: org.owasp.dependencycheck dependency-version: 13.0.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
LabelsThe following labels could not be found: Please fix the above issues or remove invalid values from |
Up to standards ✅🟢 Issues
|
* chore(deps): batch 12 Dependabot bumps Combines PRs #225-#236 into a single commit so the CVE/CI pipeline runs one cycle instead of twelve. Dependencies: - ch.qos.logback:logback-classic 1.6.0 -> 1.6.1 (#236) - com.mysql:mysql-connector-j 8.4.0 -> 26.7.0 (#235) - software.amazon.awssdk:secretsmanager 2.49.3 -> 2.51.2 (#234) - com.oracle.database.jdbc:ojdbc11 23.26.2.0.0 -> 23.26.3.0.0 (#231) - com.google.cloud:google-cloud-secretmanager 2.94.0 -> 2.95.0 (#227) Build plugins: - com.github.spotbugs 6.5.9 -> 6.5.10 (#233) - org.sonarqube 7.3.1.8318 -> 7.4.0.8496 (#230) - com.diffplug.spotless 8.8.0 -> 8.9.0 (#229) - org.owasp.dependencycheck 12.2.2 -> 13.0.0 (#228) - gradle-wrapper 9.6.1 -> 9.7.0 (#232) CI actions: - actions/setup-java 5.6.0 -> 5.7.0 (#226) - docker/login-action 4.5.1 -> 4.6.0 (#225) The mysql-connector-j jump crosses a versioning-scheme change (8.4 -> 26.7), so DatabaseDestinationMySqlIT was run against the new driver: 13/13 pass. Local verification: clean build green, SonarQube quality gate OK with zero blocker/critical issues. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * fix(security): keep CVE reports uploadable after depcheck 13.0.0 dependency-check-gradle changed the DependencyCheckExtension outputDirectory default from "reports" (12.2.2) to "dependency-check" (13.0.0), so reports landed in build/dependency-check/ while CI globs **/build/reports/dependency-check-report.html. actions/upload-artifact only warns when a glob matches nothing, so the Security Scan stayed green while uploading no CVE report at all. Pin outputDirectory to build/reports so the location no longer depends on a plugin default, and set if-no-files-found: error so a missing security report fails the job instead of passing unnoticed. Note: outputDirectory is a DirectoryProperty in 13.0.0, so it takes a File rather than the String the older API accepted. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * docs(security): record the 2026-08-16 CVE scan state The batched dependency bumps are CVE-neutral: the finding set is identical before and after, and every suppression-relevant component resolves at the same version (azure-identity 1.18.4, msal4j 1.23.1, azure-core 1.58.1, keyvault-secrets 4.11.1, httpclient5 5.6.2, httpcore5/h2 5.4.3). netty stays forced at 4.1.136.Final under awssdk 2.51.2. Two facts the scan surfaced that were not documented: - CVE-2026-64607 (httpclient5 5.6.2, MEDIUM 5.3) is a live, unsuppressed finding that predates this batch. It sits below the CVSS 7.0 gate, so it never failed a run and was never written down. Now listed in the README. - The classic-httpcore and netty CVE-2026-56816 suppressions no longer match anything on either main or this branch; NVD has narrowed both CPE ranges. They are kept until their existing expiry rather than deleted, since the affected artifacts are still resolved and NVD CPE data has flipped back before. The expiry already forces a re-review. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Bumps org.owasp.dependencycheck from 12.2.2 to 13.0.0.
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 commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)