Repository navigation
Conversation
|
No actionable comments were generated in the recent review.
|
| Layer / File(s) | Summary |
|---|---|
Pin modules and update shading assertion core/build.gradle, core/src/jarFileTest/java/org/testcontainers/JarFileShadingTest.java |
The build forces bcprov-jdk18on, bcutil-jdk18on, and bcpkix-jdk18on to version 1.86. The shading test now expects LICENSE.md in the META-INF directory listing. |
Priority:
Estimated code review effort: 2 (Simple) | ~8 minutes
Change: Other · Severity of issue fixed: High
Suggested reviewers: eddumelendez
Merge Risk: 
Minimal · up to b2834
-
The scoped dependency pinning and shading-test update present no established merge-blocking risk; normal CI should confirm the final shaded resource set.
Pre-merge checks: 
4 · 
1
-
Failed checks: 1 warning Passed checks: 4 passed-
Full details: Description check
-
Explanation
The description explains the security problem, identifies the affected versions, describes the dependency pinning and test update, references issue
#12135, and documents verification results and remaining test limitations.
Full details: Linked Issues check
-
Explanation
Issue
#12135requires a consistent fixed Bouncy Castle set in the shaded core JAR and an updated resource assertion.core/build.gradlenow forcesbcprov-jdk18on,bcutil-jdk18on, andbcpkix-jdk18onto1.86.JarFileShadingTestnow expectsLICENSE.mdin theMETA-INFlisting. These changes implement the coding objectives in#12135.
Full details: Out of Scope Changes check
-
Explanation
The whole-PR diff contains only the three Bouncy Castle version forces in
core/build.gradleand the relatedJarFileShadingTestresource expectation. The changes support the scope of#12135. No unrelated implementation or test changes are present.
-
Full details: Docstring Coverage
-
Explanation
Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 1 files. (1 skipped: 1 unsupported.)
Resolution
Write docstrings for the functions missing them to satisfy the coverage threshold.
-
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
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 @coderabbitai help to get the list of available commands.
Fixes #12135.
Problem
Testcontainers 2.0.5 embeds Bouncy Castle 1.82 from
docker-java-corein the shaded core JAR. A downstream dependency override cannot replace the relocated classes. Version 1.82 is within the affected ranges of CVE-2026-12185, CVE-2026-5598, CVE-2026-58059, and CVE-2026-59645.Change
bcprov-jdk18on,bcutil-jdk18on, andbcpkix-jdk18ontogether at 1.86.JarFileShadingTestfor theLICENSE.mdresource supplied by the newer Bouncy Castle JAR.This branch is based on
mainand leaves Jackson unchanged. docker-java PR #2696 proposes the same upstream version bump but is still open.Verification
:testcontainers:dependencies --configuration shadedresolves all three Bouncy Castle modules at 1.86 while Jackson remains at themainbaseline of 2.18.4.:testcontainers:build -x :testcontainers:test -x :testcontainers:spotlessJavaCheckpasses on the fork'smainbaseline, including compilation, shaded JAR tests, Checkstyle, Javadoc, and japicmp.git diff --checkpasses.The Docker integration suite has not completed locally: earlier runs hit Docker Model Runner and MCP gateway failures and an image-context streaming stall. The Java Spotless check could not run because
npmis unavailable on this host. CI should run the complete checks before merge.Summary by CodeRabbit
These are maintenance changes; no user-facing features or behavior changes are noted.