Skip to content

chore(deps): update dependency org.mock-server:mockserver-netty-no-dependencies to v9.4.0 - #2717

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/org.mock-server-mockserver-netty-no-dependencies-9.x
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/org.mock-server-mockserver-netty-no-dependencies-9.x

Conversation

@renovate

@renovate renovate Bot commented Nov 21, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
org.mock-server:mockserver-netty-no-dependencies (source) 9.3.0 → 9.4.0 age confidence

Release Notes

mock-server/mockserver-monorepo (org.mock-server:mockserver-netty-no-dependencies)

v9.4.0

Security
  • Every Docker image now runs a Java runtime with the fix for CVE-2026-114938, a memory-corruption bug in how JDK 17.0.6 and later, 21, 25, 26 and 27 decode Base64 on x86-64 processors with AVX-512. MockServer decodes Base64 sent by clients, such as an expectation's base64Bytes and gRPC-Web text bodies, before checking any credentials. On x86-64 the standard, -aot, -graaljs, -http3, snapshot and root images and the mockserver-webhook image run Eclipse Temurin 27.0.1.1, and the -clustered image runs Temurin 21.0.13.1; the ARM64 images, which the bug does not affect, run the newest Temurin ARM64 build (27.0.1.0.2, and 21.0.13 for -clustered). The images therefore do not set the -XX:-UseBASE64Intrinsics workaround. The binary bundle, which still carries its own Temurin 21 runtime, starts Java with -XX:-UseBASE64Intrinsics after MOCKSERVER_JAVA_OPTS in bin/mockserver and bin/mockserver.bat, and mockserver-node and the VS Code extension, which start the bundled Java themselves, put it in the same place. The Maven plugin's runForked goal and mockserver-node running the jar on your own Java pass it too, before your JVM options. The option switches off the optimised Base64 encoder and decoder, and results are unchanged. Security researchers recommend it and the JDK vendors have not yet confirmed it, and remote code execution has not been demonstrated. If you run MockServer on your own Java (the executable JAR, the WAR, the Maven plugin, JUnit, Spring or the Java API), update to a fixed JDK (Oracle or Eclipse Temurin 17.0.21.1, 21.0.13.1, 25.0.5.1 or 27.0.1.1, Amazon Corretto 17.0.21.1.2, or a fixed Azul build) or add the option yourself; see the security notice
  • customJsonUnitMatchersClass can only be set at startup (BREAKING for anyone who changes customJsonUnitMatchersClass with PUT /mockserver/configuration or a client's updateConfiguration; see upgrading to 9). This setting names the class MockServer loads and creates to supply custom json-unit matchers, but a PUT /mockserver/configuration could change it on a running server, and MockServer created the named class before checking that it implements CustomJsonUnitMatcherProvider. So anyone who could reach the control plane could make MockServer run the static initialiser and no-argument constructor of almost any class on its classpath. A PUT that sets a different value is now still answered, but the value is ignored, a warning is logged and GET /mockserver/configuration reports the value in force; a PUT that sends the value already in force logs nothing. Set it before the server starts with a system property, environment variable, mockserver.properties or Configuration. MockServer also now ignores, with the same warning as before, a named class that does not implement CustomJsonUnitMatcherProvider without running any of its code.
  • Agent skills: dockerhub-credentials no longer asks for the Docker Hub token in the chat or puts it on a command line; you now enter it at a hidden prompt in your own terminal, and it reaches AWS Secrets Manager through a private temporary file (#​3027). pr-monitor now only reports when asked to monitor or watch PRs, and merges only when asked to merge (its script needs --merge), holds merges while a release is in progress, and no longer hides its status report (#​3028)
Added
Changed
  • Every Docker image except -clustered now runs Java 27: Eclipse Temurin from a checksum-pinned Adoptium download, trimmed with jlink and copied onto gcr.io/distroless/java-base-debian13. The standard and -aot images move from Java 26 and 25. The root, snapshot, -graaljs and mockserver-webhook images used the distroless Java 25 image and keep its Java modules except four that the Temurin 27 JDK no longer ships: jdk.graal.compiler, jdk.graal.compiler.management, jdk.internal.vm.ci and jdk.jsobject. The -clustered image moves from the distroless Java 21 image to a jlink-trimmed Temurin 21, because its Infinispan library cannot start on Java 24 or later, and drops jdk.internal.vm.ci, jdk.internal.vm.compiler, jdk.internal.vm.compiler.management and jdk.jsobject. Every image uses the base image's Debian trust store (/etc/ssl/certs/java/cacerts), as the distroless Java images did, so a trust store mounted there is used. The library is still compiled for Java 17. Start-up figures for the new runtime have not been re-measured yet.
  • -XX:+ZGenerational now stops the Java 27 images from starting (BREAKING for anyone who still passes it in JAVA_TOOL_OPTIONS or the Helm chart's app.jvmOptions to any image except -clustered): Java 27 no longer recognises it and exits with Unrecognized VM option 'ZGenerational', where Java 25 and 26 ignored it with a warning. Drop it; -XX:+UseZGC alone already gives generational ZGC. The -clustered image, still on Java 21, keeps -XX:+UseZGC -XX:+ZGenerational.
  • Every image's Java is now at /usr/lib/jvm/temurin-trimmed/bin/java, and on the PATH. The root, snapshot, -graaljs, -clustered and mockserver-webhook images keep /usr/bin/java as a link to it, but their arch-specific Java home (such as /usr/lib/jvm/temurin-25-jre-amd64) and the JAVA_VERSION environment variable are gone: use java on the PATH or the new path. The standard and -aot images used /usr/lib/jvm/temurin25-trimmed/bin/java, which still works as a link to the new path, so an entrypoint override copied from an older image keeps starting; switch it to the new path.
  • The -sources.jar of each -no-dependencies artifact on Maven Central (mockserver-netty-no-dependencies, mockserver-client-java-no-dependencies, mockserver-junit-jupiter-no-dependencies, mockserver-junit-rule-no-dependencies and mockserver-spring-test-listener-no-dependencies) now holds only MockServer's own sources, so it is a few MB instead of 34 to 51 MB. It used to also hold the sources of every library those jars bundle. To read a bundled library's sources, use that library's own -sources.jar. The library is renamed under shaded_package in the jar, but its sources keep the original package names.
  • mockserver-junit-jupiter-no-dependencies, mockserver-junit-rule-no-dependencies and mockserver-spring-test-listener-no-dependencies keep their names but no longer each carry a full copy of the MockServer server (about 87 MB each). Each jar now holds only its own classes and brings in mockserver-netty-no-dependencies as a dependency, which Maven and Gradle download for you, so build files need no change; if you also listed mockserver-netty-no-dependencies, you no longer get two copies of every MockServer class. Three things now match mockserver-netty-no-dependencies: HTTPS uses Java's built-in TLS instead of bundled OpenSSL libraries; a module-info.java that uses ClientAndServer or MockServerClient also needs requires org.mockserver.netty;; and a project with no SLF4J provider now gets MockServer's log output through java.util.logging. See Upgrading to 9.0.0.
  • The CycloneDX software bill of materials on Maven Central is now one file covering every released module and its dependencies, at org/mock-server/mockserver/<version>/mockserver-<version>-cyclonedx.json (for example https://repo1.maven.org/maven2/org/mock-server/mockserver/<version>/mockserver-<version>-cyclonedx.json). This applies from the release after 9.3.0. 9.3.0 published a separate <artifactId>-<version>-cyclonedx.json next to each module, and its mockserver-9.3.0-cyclonedx.json covers only the parent POM. From the next release, fetch the single file instead. The single file covers the Maven plugin too.
Fixed
  • maxLoggedMatchFailures now also limits requests served by a forward expectation. After the upstream answered, mock drift detection (on by default) checked the request against every expectation again and logged a "didn't match expectation" line for each one, with no limit and no "further did-not-match entries were not logged" summary, so one forwarded request could log a line per configured expectation, including a second "matched expectation" line. That check no longer logs match results; the request's own matching still logs them, within the limit. gRPC bidirectional-streaming requests, whose routing check logged every expectation it tried before the request's own matching logged them again, no longer log them twice either. PUT /mockserver/pact/verify no longer writes a per-expectation match entry for each interaction either; its result reports the outcome (#​3020)
  • maxLoggedMatchFailures now also limits the "didn't match expectation" lines logged when MockServer checks an HTTP/1.1 request against respondBeforeBody expectations before its body arrives. That check logged a line for every respondBeforeBody expectation it tried, with no limit, and when none of them answered the request, the request's normal matching then logged them again. A request answered by a respondBeforeBody expectation now logs the expectations it was checked against within the limit, then the "matched expectation" line; any other request is logged once, by its normal matching (#​3020)
  • (Release) The release preflight now checks the NuGet API key live on nuget.org instead of only checking that the secret exists. It flags a key that has expired or been revoked, or that cannot push MockServerClient or MockServer.Testcontainers. nuget.org now limits API keys to 30 days, and an expired key failed both NuGet publish jobs in the 9.3.0 release. The publish-secrets runbook now gives the 30-day expiry and the rotation steps.
  • (Release) A release can no longer half-publish to Maven Central. mockserver-maven-plugin was published in a second Central deployment after the other Maven artifacts, so when the first deployment used up Sonatype's monthly publishing limit the plugin was refused, which is why the 9.3.0 Maven plugin did not go live with the rest of 9.3.0. The plugin now ships in the same deployment as every other module, and before publishing the release checks Sonatype's validation warnings: if they say a publishing limit is exceeded or publishing is blocked, it drops the deployment and stops with nothing published. Warnings that only say a limit is being approached are printed and the release continues.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added the dependencies Pull requests that update a dependency file label Nov 21, 2026
@renovate
renovate Bot enabled auto-merge (squash) November 21, 2026 03:29

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants