build(deps): bump build plugins and analysis tooling to current - #155
Merged
Conversation
Pure version maintenance, no behaviour change. Two groups: Cross-repo drift, closed. The four sibling repos deliberately run the same toolchain versions, and BitcoinAddressFinder pulled ahead when its Dependabot PRs were merged. This brings the rest back in step: maven-compiler-plugin 3.15.0 -> 3.16.0 maven-surefire-plugin 3.5.6 -> 3.6.0 nullaway 0.14.0 -> 0.14.1 Behind current upstream in all four repos: git-commit-id-maven-plugin 10.0.0 -> 10.0.1 spotless-maven-plugin 3.10.1 -> 3.10.2 spotbugs-maven-plugin 4.10.4.0 -> 4.10.4.1 checker / checker-qual 4.2.2 -> 4.2.3 Note the checker bump moves ONE property that feeds both the annotation processor and the qualifiers. That is deliberate and must stay that way: the Nullness Checker resolves its own qualifiers through javac's symbol table, so processor and checker-qual have to share a major version -- the lesson from the reverted 3.55.1 pin in java-llama.cpp. Deliberately NOT bumped: jqwik stays at 1.9.3. Releases from 1.10.0 on print a prompt-injection string aimed at AI coding agents, and the workspace policy (policies/jqwik-prompt-injection.md) requires rejecting any PR that moves it. Dependabot will keep proposing it. Verified locally: mvn clean verify green (288 tests), PIT 179/179 mutations killed (100%), the class-file gate clean over target (500 classes, 0 above major 52), and spotless 3.10.2 reformats nothing -- the working tree after `spotless:apply` holds only the pom edit itself. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01AnNYn8W1xuVxVJtyL34GyH
bernardladenthin
had a problem deploying
to
maven-central
September 5, 2026 10:58 — with
GitHub Actions
Failure
bernardladenthin
had a problem deploying
to
maven-central
September 5, 2026 10:58 — with
GitHub Actions
Failure
Review SummaryThis is a well-structured dependency maintenance PR. The changes are limited to version updates in pom.xml with clear, deliberate reasoning. ✅ Strengths
Patch updates (low risk)
Minor updates (still low risk for build tooling)
Deliberately NOT updated
✅ Ready to merge — High-quality maintenance PR with sound reasoning and comprehensive verification. |
|
8 tasks
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #155 +/- ##
=========================================
Coverage 96.88% 96.88%
Complexity 94 94
=========================================
Files 1 1
Lines 257 257
Branches 33 33
=========================================
Hits 249 249
Misses 2 2
Partials 6 6 ☔ View full report in Codecov by Harness. |
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.



Summary
Pure version maintenance, no behaviour change. One of four coordinated PRs (jllama / srcmorph / BAF / streambuffer).
Cross-repo drift, closed. The four sibling repos deliberately run the same toolchain versions; BitcoinAddressFinder pulled ahead when its Dependabot PRs were merged.
maven-compiler-pluginmaven-surefire-pluginnullawayBehind current upstream in all four repos.
git-commit-id-maven-pluginspotless-maven-pluginspotbugs-maven-pluginchecker/checker-qualNo
lombokand noslf4jrows here — this repo uses neither.The checker bump moves one property that feeds both the annotation processor and the qualifiers, and that coupling is the point: the Nullness Checker resolves its own qualifiers through javac's symbol table, so the two must share a major version — the lesson from the 3.55.1 pin reverted in java-llama.cpp.
Deliberately NOT bumped:
jqwikstays at 1.9.3. Releases from 1.10.0 on print a prompt-injection string aimed at AI coding agents, and the workspace policy requires rejecting any PR that moves it. Dependabot will keep proposing it.Test plan
mvn clean verifygreen — 288 tests, 0 failures (includes the jqwik properties and the Lincheck linearizability run)target: 500 classes, 0 above major 52spotless3.10.2 reformats nothing — the working tree afterspotless:applyholds only the pom editRelated PRs
Same change in java-llama.cpp, srcmorph and BitcoinAddressFinder (category 2 only — BAF already carries category 1).
Checklist
CONTRIBUTING.mdandCODE_OF_CONDUCT.md🤖 Generated with Claude Code
https://claude.ai/code/session_01AnNYn8W1xuVxVJtyL34GyH
Generated by Claude Code