chore: update dependencies and document spotbugs findings - #209
Merged
Merged
Conversation
…v-scanner-action v2.6.0
Cross-repo dependency sweep of 2026-09-20.
palantir-java-format 2.97.0 -> 2.98.0 all three modules (spotless formatter;
bumped in all four sibling repos together)
exec-maven-plugin 3.6.3 -> 3.6.4 srcmorph-maven-plugin (closes drift: BAF
and streambuffer already carried 3.6.4)
google/osv-scanner-action v2.5.1 -> v2.6.0 the reusable workflows
CLAUDE.md's dependency table said slf4j 2.0.18 while the parent has converged on
2.0.19 since #205; synced.
Deliberately NOT bumped: jqwik 1.9.3 (workspace policy), slf4j 2.0.19 (2.1.0 is
alpha-only), maven-plugin-api / maven-plugin-tools (only Maven-4 betas/RCs on offer).
The unresolvable `<llama.version>5.2.0</llama.version>` pin is unchanged — that is
a java-llama.cpp release decision tracked in TODO.md, not a version bump.
Verified as far as this repo currently allows: `mvn -pl srcmorph,srcmorph-cli,
srcmorph-maven-plugin spotless:apply` under palantir 2.98.0 changes no Java file;
with `-Dllama.version=5.2.0-SNAPSHOT` (java-llama.cpp's current main installed
locally) all three modules compile and the reactor reaches spotbugs:check. That
step then fails on 4 pre-existing findsecbugs findings in
LlamaCppJniProviderSupport — reproduced identically on the unmodified origin/main
tree, so not caused here. Recorded in TODO.md next to the 5.2.0 blocker it hides
behind, because it will be the next red the moment that pin resolves.
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01FbGmAZY9bwxox72iU13HvJ
bernardladenthin
had a problem deploying
to
maven-central
September 20, 2026 11:32 — with 
GitHub Actions
Failure
GitHub Actions
Failure
bernardladenthin
had a problem deploying
to
startgate
September 20, 2026 11:32 — with
GitHub Actions
Error
GitHub Actions
Error
bernardladenthin
had a problem deploying
to
maven-central
September 20, 2026 11:32 — with
GitHub Actions
Failure
GitHub Actions
Failure
This branch had an error being deployed
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
2 participants
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
srcmorphthat will surface once thellama5.2.0 dependency pin resolves, with guidance on remediationosv-scanner-actionfrom v2.5.1 to v2.6.0palantir-java-formatfrom 2.97.0 to 2.98.0 across all modulesexec-maven-pluginfrom 3.6.3 to 3.6.4Test plan
Related issues / PRs
Checklist
CONTRIBUTING.mdandCODE_OF_CONDUCT.mdSECURITY.md)https://claude.ai/code/session_01FbGmAZY9bwxox72iU13HvJ