Repository navigation
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
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
…pendencies to v9.4.0
renovate
Bot
requested review from
dhoard,
fstab,
jaydeluca and
zeitlinger
as code owners
November 21, 2026 03:29
This branch has not been 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
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.
This PR contains the following updates:
9.3.0→9.4.0Release Notes
mock-server/mockserver-monorepo (org.mock-server:mockserver-netty-no-dependencies)
v9.4.0Security
base64Bytesand gRPC-Web text bodies, before checking any credentials. On x86-64 the standard,-aot,-graaljs,-http3, snapshot and root images and themockserver-webhookimage run Eclipse Temurin 27.0.1.1, and the-clusteredimage 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:-UseBASE64Intrinsicsworkaround. The binary bundle, which still carries its own Temurin 21 runtime, starts Java with-XX:-UseBASE64IntrinsicsafterMOCKSERVER_JAVA_OPTSinbin/mockserverandbin/mockserver.bat, andmockserver-nodeand the VS Code extension, which start the bundled Java themselves, put it in the same place. The Maven plugin'srunForkedgoal andmockserver-noderunning 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 noticecustomJsonUnitMatchersClasscan only be set at startup (BREAKING for anyone who changescustomJsonUnitMatchersClasswithPUT /mockserver/configurationor a client'supdateConfiguration; see upgrading to 9). This setting names the class MockServer loads and creates to supply custom json-unit matchers, but aPUT /mockserver/configurationcould change it on a running server, and MockServer created the named class before checking that it implementsCustomJsonUnitMatcherProvider. 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. APUTthat sets a different value is now still answered, but the value is ignored, a warning is logged andGET /mockserver/configurationreports the value in force; aPUTthat sends the value already in force logs nothing. Set it before the server starts with a system property, environment variable,mockserver.propertiesorConfiguration. MockServer also now ignores, with the same warning as before, a named class that does not implementCustomJsonUnitMatcherProviderwithout running any of its code.dockerhub-credentialsno 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-monitornow 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
-clusterednow runs Java 27: Eclipse Temurin from a checksum-pinned Adoptium download, trimmed with jlink and copied ontogcr.io/distroless/java-base-debian13. The standard and-aotimages move from Java 26 and 25. The root, snapshot,-graaljsandmockserver-webhookimages 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.ciandjdk.jsobject. The-clusteredimage 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 dropsjdk.internal.vm.ci,jdk.internal.vm.compiler,jdk.internal.vm.compiler.managementandjdk.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:+ZGenerationalnow stops the Java 27 images from starting (BREAKING for anyone who still passes it inJAVA_TOOL_OPTIONSor the Helm chart'sapp.jvmOptionsto any image except-clustered): Java 27 no longer recognises it and exits withUnrecognized VM option 'ZGenerational', where Java 25 and 26 ignored it with a warning. Drop it;-XX:+UseZGCalone already gives generational ZGC. The-clusteredimage, still on Java 21, keeps-XX:+UseZGC -XX:+ZGenerational./usr/lib/jvm/temurin-trimmed/bin/java, and on thePATH. The root, snapshot,-graaljs,-clusteredandmockserver-webhookimages keep/usr/bin/javaas a link to it, but their arch-specific Java home (such as/usr/lib/jvm/temurin-25-jre-amd64) and theJAVA_VERSIONenvironment variable are gone: usejavaon thePATHor the new path. The standard and-aotimages 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.-sources.jarof each-no-dependenciesartifact on Maven Central (mockserver-netty-no-dependencies,mockserver-client-java-no-dependencies,mockserver-junit-jupiter-no-dependencies,mockserver-junit-rule-no-dependenciesandmockserver-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 undershaded_packagein the jar, but its sources keep the original package names.mockserver-junit-jupiter-no-dependencies,mockserver-junit-rule-no-dependenciesandmockserver-spring-test-listener-no-dependencieskeep 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 inmockserver-netty-no-dependenciesas a dependency, which Maven and Gradle download for you, so build files need no change; if you also listedmockserver-netty-no-dependencies, you no longer get two copies of every MockServer class. Three things now matchmockserver-netty-no-dependencies: HTTPS uses Java's built-in TLS instead of bundled OpenSSL libraries; amodule-info.javathat usesClientAndServerorMockServerClientalso needsrequires 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.org/mock-server/mockserver/<version>/mockserver-<version>-cyclonedx.json(for examplehttps://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.jsonnext to each module, and itsmockserver-9.3.0-cyclonedx.jsoncovers only the parent POM. From the next release, fetch the single file instead. The single file covers the Maven plugin too.Fixed
maxLoggedMatchFailuresnow 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/verifyno longer writes a per-expectation match entry for each interaction either; its result reports the outcome (#3020)maxLoggedMatchFailuresnow also limits the "didn't match expectation" lines logged when MockServer checks an HTTP/1.1 request againstrespondBeforeBodyexpectations before its body arrives. That check logged a line for everyrespondBeforeBodyexpectation 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 arespondBeforeBodyexpectation 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)MockServerClientorMockServer.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.mockserver-maven-pluginwas 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)
🚦 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.
This PR was generated by Mend Renovate. View the repository job log.