chore(deps): bump junit-jupiter to 6.1.2 and spotbugs-maven-plugin to 4.10.3.0#640
Merged
Conversation
… 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>
bundolee
requested review from
LonelyMidoriya,
MaximPlusov,
hnc-jglee and
hyunhee-jo
as code owners
July 14, 2026 08:59
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughThe Maven configuration updates the JUnit Jupiter version from ChangesMaven Version Updates
Estimated code review effort: 1 (Trivial) | ~2 minutes Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
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. Comment |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.xmlagainst 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.2spotbugs-maven-plugin: 4.10.2.0 → 4.10.3.0Everything else is already at its latest stable and was left untouched: veraPDF
validation-model/wcag-validation1.31.99,wcag-algorithms1.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-compiler4.0.0-beta-4, surefire3.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):
mvn clean packageafter bumpmvn test(all modules)🤖 Generated with Claude Code
Summary by CodeRabbit