Skip to content

chore(deps): bump junit-jupiter to 6.1.2 and spotbugs-maven-plugin to 4.10.3.0#640

Merged
bundolee merged 1 commit into
mainfrom
chore/bump-deps-junit-spotbugs
Jul 14, 2026
Merged

chore(deps): bump junit-jupiter to 6.1.2 and spotbugs-maven-plugin to 4.10.3.0#640
bundolee merged 1 commit into
mainfrom
chore/bump-deps-junit-spotbugs

Conversation

@bundolee

@bundolee bundolee commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

Objective

Keep the Java build on the latest stable releases of its test and static-analysis tooling, so contributors pick up current bug fixes and the project doesn't drift onto unsupported versions.

Approach

Audited every version property and plugin in java/pom.xml against authoritative sources — Maven Central release metadata for Central-hosted artifacts, and the vera-dev artifactory for the veraPDF family (veraPDF is not mirrored to Central at current versions).

Only the two artifacts with a newer stable release were bumped:

  • junit-jupiter: 6.1.1 → 6.1.2
  • spotbugs-maven-plugin: 4.10.2.0 → 4.10.3.0

Everything else is already at its latest stable and was left untouched: veraPDF validation-model/wcag-validation 1.31.99, wcag-algorithms 1.31.33, jackson-databind 2.22.1, okhttp 5.4.0, commons-cli 1.11.0, and the remaining Maven plugins.

Pre-release versions that exist for a few tools (assertj 4.0.0-M1, maven-compiler 4.0.0-beta-4, surefire 3.6.0-M1, source/deploy betas) were intentionally not adopted — a published library should not ship on milestones/betas.

Evidence

Ran the real build and full test suite after the bump (not just an assertion that the pom changed):

Scenario Expected Actual
mvn clean package after bump Build succeeds BUILD SUCCESS
mvn test (all modules) 0 failures / 0 errors 0 failures / 0 errors, exit 0
veraPDF resolution unchanged Same versions resolve 1.31.99 / 1.31.33 resolve as before

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Chores
    • Updated project build and testing tools to newer versions.
    • Improved compatibility with the latest development and quality-checking workflows.
    • No user-facing functionality or interface changes were introduced.

… 4.10.3.0

Objective: The build should track the latest stable releases of its test
and static-analysis tooling so contributors get current bug fixes and
avoid drifting onto unsupported versions.

Approach: Audited every version property and plugin in java/pom.xml
against the authoritative sources — Maven Central release metadata for
Central-hosted artifacts and the vera-dev artifactory for the veraPDF
family. Only the two artifacts that had a newer *stable* release were
bumped: junit-jupiter 6.1.1 -> 6.1.2 and spotbugs-maven-plugin
4.10.2.0 -> 4.10.3.0. Everything else (veraPDF 1.31.99 / wcag-algorithms
1.31.33, jackson, okhttp, commons-cli, and the remaining plugins) is
already at its latest stable, so it was left untouched. Pre-release
versions that exist for assertj (4.0.0-M1), maven-compiler (4.0.0-beta-4),
surefire (3.6.0-M1), source, and deploy were intentionally skipped — a
published library should not ship on milestones/betas.

Evidence: Ran the real build and full test suite after the bump.
Before: pom pinned junit 6.1.1 / spotbugs 4.10.2.0.
After: `mvn clean package` succeeds and `mvn test` passes with 0
failures / 0 errors across all modules (exit 0).

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Jul 14, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 169eb15e-3a8e-4554-ace6-351d8bc8db4c

📥 Commits

Reviewing files that changed from the base of the PR and between bbeeb81 and 55fe1a4.

📒 Files selected for processing (1)
  • java/pom.xml

Walkthrough

The Maven configuration updates the JUnit Jupiter version from 6.1.1 to 6.1.2 and the SpotBugs Maven plugin version from 4.10.2.0 to 4.10.3.0.

Changes

Maven Version Updates

Layer / File(s) Summary
Update Maven tool versions
java/pom.xml
Updates the JUnit Jupiter and SpotBugs Maven plugin property values.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Suggested reviewers: maximplusov, lonelymidoriya, hnc-jglee, hyunhee-jo

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately summarizes the only changes: bumping JUnit Jupiter and SpotBugs plugin versions in the Java POM.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@bundolee
bundolee merged commit 2bd7466 into main Jul 14, 2026
8 checks passed
@bundolee
bundolee deleted the chore/bump-deps-junit-spotbugs branch July 14, 2026 09:03
@codecov

codecov Bot commented Jul 14, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

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