-
Notifications
You must be signed in to change notification settings - Fork 22
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Checking mergeability…
Don’t worry, you can still create the pull request.
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: keploy/java-sdk
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: main
Could not load branches
Nothing to show
Loading
...
head repository: keploy/java-sdk
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: docs/java-version-support
Could not load branches
Nothing to show
Loading
- 1 commit
- 1 file changed
- 1 contributor
Commits on Aug 18, 2026
-
docs: document the supported Java ceiling and where it comes from
The README said only 'Supported runtimes in CI today are Java 8, 17, and 21', which is a CI matrix, not a support statement — it says nothing about the highest Java version dynamic dedup can actually handle, and nothing about this repo being part of that limit. That gap is not academic. Dedup needs BOTH jars to read the app's bytecode: the jacocoagent in k8s-proxy's init image to analyze coverage, and the ASM shaded into keploy-sdk.jar (via org.jacoco:org.jacoco.core) to instrument it. The lower of the two wins, and while jacoco.core sat on 0.8.12 the lower one was THIS repo — it capped dedup at Java 22 while the agent could already read more, with nothing recording that the SDK was the binding constraint. Above the ceiling nothing fails loudly: the app is instrumented, the replay passes, and coverage is simply never produced, so no duplicates are found and it looks like the app has none. Documents the two-jar ceiling, why exceeding it is silent, and the exact two-repo procedure for raising it — including taking JaCoCo's OFFICIALLY supported version rather than the experimental one, since the shipped ASM declares one version beyond what it accepts by default. Signed-off-by: Shubham Jain <shubham@keploy.io>
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff main...docs/java-version-support