Skip to content

chore(deps): batch 12 Dependabot bumps (#225-#236) - #237

Merged
mferretti merged 3 commits into
mainfrom
chore/dependabot-batch-aug
Aug 16, 2026
Merged

chore(deps): batch 12 Dependabot bumps (#225-#236)#237
mferretti merged 3 commits into
mainfrom
chore/dependabot-batch-aug

Conversation

@mferretti

Copy link
Copy Markdown
Owner

Combines the 12 open Dependabot PRs into a single commit so the CVE/CI pipeline runs one cycle instead of twelve.

Supersedes #225, #226, #227, #228, #229, #230, #231, #232, #233, #234, #235, #236.

Dependencies

Artifact From To PR
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

Plugin From To PR
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

Action From To PR
actions/setup-java 5.6.0 5.7.0 #226
docker/login-action 4.5.1 4.6.0 #225

Verification

  • ./gradlew clean build — green on Gradle 9.7.0, spotless 8.9.0, spotbugs 6.5.10.
  • DatabaseDestinationMySqlIT — 13/13 pass. Run explicitly because mysql-connector-j crosses a versioning-scheme change (8.4 → 26.7); the driver is otherwise not exercised by unit tests.
  • SonarQube quality gate — OK, zero blocker/critical issues.
  • org.owasp.dependencycheck 13.0.0 — extension config resolves and the dependencyCheckAnalyze task configures cleanly against the existing suppression file.

No interaction with the resolutionStrategy.force block: none of the forced artifacts (log4j, commons-lang3, httpcore5-h2, jackson-databind, netty) are in this batch.

OWASP dependency-check is skipped on PRs, so it will be triggered separately via workflow_dispatch on this branch before merge.

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>
@codacy-production

codacy-production Bot commented Aug 16, 2026

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity · 2 duplication

Metric Results
Complexity 0
Duplication 2

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

mferretti and others added 2 commits August 16, 2026 18:26
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>
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant