You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@artemis.apache.org by "dependabot[bot] (via GitHub)" <gi...@apache.org> on 2026/10/19 02:28:36 UTC
[PR] ARTEMIS-X Bump mockserver.version from 8.0.0 to 9.0.0 [artemis]
dependabot[bot] opened a new pull request, #6806:
URL: https://github.com/apache/artemis/pull/6806
Bumps `mockserver.version` from 8.0.0 to 9.0.0.
Updates `org.mock-server:mockserver-netty` from 8.0.0 to 9.0.0
Updates `org.mock-server:mockserver-core` from 8.0.0 to 9.0.0
<details>
<summary>Release notes</summary>
<p><em>Sourced from <a href="https://github.com/mock-server/mockserver-monorepo/releases">org.mock-server:mockserver-core's releases</a>.</em></p>
<blockquote>
<h2>MockServer 9.0.0</h2>
<h2>[9.0.0] - 2026-10-15</h2>
<p>This release delivers a sustained performance and memory programme alongside data-integrity fixes under load, plus a large set of LLM-provider correctness fixes, dashboard improvements, and client-library parity work. Headline numbers from the single-load-generator benchmark on the same six-core rig (builds 420 and 464): the healthy ceiling rises from 39,033 to 57,149 req/s and the peak from 43,671 to 59,905 req/s, with p95 at 32,000 req/s falling from 56.6 ms to 0.44 ms on the new ZGC default in the Docker images; event-log retained heap at 20,000 entries falls from 429 MB to 61 MB; Docker image download shrinks ~23%; and instance shutdown drops from ~107 ms to near zero. 22 BREAKING changes affect HTTP/3, DNS mocking, binary (non-HTTP) proxying and binary expectation matching while proxying, template-failure response codes, <code>maxLoggedMatchFailures</code>'s default, initialisation-file <code>id</code> conflicts, the Node client's TypeScript typings and <code>exports</code
> map, <code>LOG_ENTRIES</code> log output, control-plane error handling and mTLS, the Rust client's enums, verification-failure wording, response <code>statusCode</code> validation, AsyncAPI and response/OpenAPI verification, GenAI trace span names, the Node client's recorded-request typings, and the Go client/Testcontainers module's <code>/v9</code> module paths — see <em>Upgrading from 8.0.0</em> and the <code>BREAKING</code> entries under <em>Changed</em>. For a per-change migration list, see the upgrade guide at <a href="https://www.mock-server.com/mock_server/upgrading_to_9.html">https://www.mock-server.com/mock_server/upgrading_to_9.html</a>.</p>
<table>
<thead>
<tr>
<th>Metric</th>
<th>Before</th>
<th>After</th>
</tr>
</thead>
<tbody>
<tr>
<td>Throughput, healthy ceiling / peak (req/s, 6 cores)</td>
<td>39,033 / 43,671</td>
<td>57,149 / 59,905</td>
</tr>
<tr>
<td>p95 latency at 32,000 / 48,000 req/s offered</td>
<td>56.6 ms / 82.4 ms</td>
<td>0.44 ms / 12.0 ms</td>
</tr>
<tr>
<td>Event-log heap (20,000 entries)</td>
<td>429 MB</td>
<td>61 MB</td>
</tr>
<tr>
<td>Docker image download (linux/arm64, standard image)</td>
<td>~167 MB</td>
<td>~129 MB</td>
</tr>
<tr>
<td>Instance shutdown time</td>
<td>~107 ms</td>
<td>~0 ms</td>
</tr>
</tbody>
</table>
<p>"Before" is perf build 420 (commit d568695a2, 2026-09-24, JDK 17.0.20, G1 collector), measured nine days after the 8.0.0 tag and already carrying some of this release's own work, since 8.0.0 itself was never measured on this rig. "After" is perf build 464 (commit efdc5227b2, 2026-09-27, JDK 25, ZGC), the performance page's single-load-generator figures; the page's headline is now a different, multi-generator measurement (see <em>Changed</em>). Both are comparable with each other but not with any benchmark published after this release.</p>
<h4>Upgrading from 8.0.0</h4>
<ul>
<li><strong>Go client and Go Testcontainers module users</strong>: both modules move to <code>/v9</code> module paths (the Go module proxy refused their 8.0.0 tags) — run <code>go get github.com/mock-server/mockserver-monorepo/mockserver-client-go/v9</code> (and the Testcontainers module's <code>/v9</code> path if you use it) and change your
imports from the <code>/v7</code>/unsuffixed paths to the <code>/v9</code> ones; see <em>Changed</em>.</li>
<li><strong>HTTP/3 users</strong> (<code>http3Port</code> set): the QUIC native library now ships separately — use the <code>-jar-with-dependencies-http3</code> jar or the <code>mockserver/mockserver:<version>-http3</code> Docker image (<code>latest-http3</code>, <code>snapshot-http3</code>; Helm: <code>image.variant=http3</code>), and a server that cannot serve HTTP/3 (missing
native, or the port unusable) now refuses to start instead of silently falling back.</li>
<li><strong>DNS mocking users</strong> (<code>dnsEnabled=true</code>): MockServer now refuses to start if its <code>dnsPort</code> cannot be bound, instead of logging a warning and running without DNS. Leave <code>dnsPort</code> at its default of <code>0</code> to let the OS pick a free port, or set <code>dnsEnabled=false</code>.</li>
<li><strong>TypeScript users of <code>mockserver-client/llm</code></strong>: the deep-import typings no longer declare a default export; import from <code>mockserver-client</code> itself, use <code>import llm = require(...)</code>/<code>import * as llm from ...</code>, or turn on <code>esModuleInterop</code> (see <em>Changed</em>).</li>
<li><strong>Binary (non-HTTP) proxy users</strong>: a client connection now always keeps one upstream connection for its whole life — forwarding one message per upstream connection is removed, along with its <code>forwardBinaryRequestsWithoutWaitingForResponse</code> setting (a value still set is ignored, with a warning); remove it from your configuration.</li>
<li><strong>Anyone reading a request or response body from <code>message</code>/<code>arguments</code> of <code>LOG_ENTRIES</code> output</strong> (including the MCP <code>retrieve_logs</code>/<code>raw_retrieve</code> tools): read it from the entry's <code>httpRequest</code>/<code>httpResponse</code> instead — <code>message</code>/<code>arguments</code> now refer to that request/response by a short form
such as <code>"POST /orders"</code> or <code>"201"</code>.</li>
<li><strong>Anyone treating a control-plane <code>400</code> as any failure</strong>, or catching the Java client's <code>IllegalArgumentException</code> for non-input failures: an unexpected server-side fault is now a <code>500</code> with a generic message and correlation id; <code>400</code> is now reserved for requests MockServer genuinely rejects. The
Java client's <code>retrieveLogsByCorrelationId</code> and <code>retrieveActiveExpectations(requestDefinition, format)</code> now throw instead of returning the error's text.</li>
<li><strong>Anyone importing a path inside <code>mockserver-client</code>/<code>mockserver-node</code> other than the package or a documented module</strong>: both packages now have an <code>exports</code> map, so an unlisted path (<code>.d.ts</code> files, <code>tasks/mockServer.js</code>, etc.) now fails to resolve — resolve <code><package>/package.json</code> and join a file's
path to that directory if you need one by location.</li>
<li><strong>Control-plane mTLS, Java client</strong>: the client now trusts only <code>controlPlaneTLSMutualAuthenticationCAChain</code> for MockServer's certificate; add MockServer's own CA to that chain if it signs the server certificate.</li>
<li><strong>Control-plane mTLS, server</strong>: MockServer now accepts only client certificates signed by <code>controlPlaneTLSMutualAuthenticationCAChain</code>; add MockServer's own CA to the chain if it signs your client certificates (or use your own CA if it's the bundled default), and MockServer now refuses to start with
mTLS required, no chain set, and the bundled default CA — set the chain or configure your own CA with <code>certificateAuthorityCertificate</code>/<code>certificateAuthorityPrivateKey</code>.</li>
<li><strong>Rust client users who <code>match</code> on its enums</strong>: every public enum is now <code>#[non_exhaustive]</code> (add a wildcard arm), and server-sent enums (<code>ResponseMode</code>, <code>BinaryUpstream</code>, <code>CrossProtocolTrigger</code>, the <code>Load*</code> enums) gain an <code>Unknown</code> variant that cannot be sent back; <code>LoadThresholdMetric</code> also gains
<code>CheckFailureRate</code>.</li>
<li><strong>Anyone asserting the exact text of an over-count verification failure</strong> (<code>never()</code>, <code>exactly</code>, <code>atMost</code>, <code>between</code>, <code>verifyZeroInteractions</code>): the message now reads "found … but should have been found …" instead of "not found".</li>
<li><strong>Anyone with a response <code>statusCode</code> of <code>0</code> or outside 100–999</strong> (most likely from a blank 8.0.0 dashboard status field): it is now rejected at creation with a <code>400</code>, or skipped with a <code>WARN</code> (naming it) when loaded from an initialization/persisted-expectations file, with the file backed up first.</li>
<li><strong>AsyncAPI verification users</strong> (<code>PUT /mockserver/asyncapi/verify</code>, or the Java client's <code>verifyAsyncMessage</code>): put <code>atLeast</code>/<code>atMost</code>/<code>exactly</code> inside <code>count</code>, not at the top level — the endpoint now answers <code>400</code> for unknown fields instead of ignoring them.</li>
<li><strong>Anyone verifying a response body with a regex, JSON path, JSON Schema, XPath, XML Schema, form, multipart, fuzzy, GraphQL, JSON-RPC, WASM or allOf matcher</strong>: that matcher is now actually applied, where it was previously ignored (verification passed whenever any recorded response had a JSON object
body).</li>
<li><strong>Anyone verifying requests with an OpenAPI matcher</strong>: only requests for the matched <code>operationId</code> now count, instead of every recorded request (<code>verifySequence</code> was unaffected).</li>
<li><strong>Anyone selecting LLM completions by <code>gen_ai.operation.name == "chat"</code></strong>: Gemini calls are now <code>generate_content</code>, and prompt-string completions (legacy <code>/v1/completions</code>, Mistral FIM, Ollama <code>/api/generate</code>, prompt-based Bedrock InvokeModel models) are now <code>text_completion</code> — update to match
<code>chat</code>, <code>generate_content</code> and <code>text_completion</code> together.</li>
<li><strong>TypeScript users of the Node client's <code>retrieveRecordedRequests</code>/<code>retrieveRecordedRequestsById</code></strong>: now typed <code>Promise<RequestDefinition[]></code> instead of <code>Promise<HttpResponse[]></code>; narrow each result to <code>HttpRequest</code> before reading HTTP-specific fields.</li>
<li><strong>Anyone proxying binary (non-HTTP) traffic while binary expectations are registered on the same MockServer</strong>: a message matching a binary expectation is now answered by it and not forwarded, by default (<code>matchBinaryExpectationsWhenProxying</code>); set it to <code>false</code> to always forward as in 8.0.0.</li>
<li><strong>Anyone relying on every "didn't match" comparison being logged</strong>: the new <code>maxLoggedMatchFailures</code> property now defaults to <code>50</code>, so at <code>INFO</code> only the first 50 "didn't match" entries per request are logged; set <code>maxLoggedMatchFailures=-1</code> to keep logging every comparison.</li>
<li><strong>Anyone with expectations in an <code>initializationJsonPath</code> file whose <code>id</code>s repeat</strong>: the file now keeps the <em>last</em> expectation for each repeated <code>id</code>, not the first; remove the repeated <code>id</code>s, or put the one you want last.</li>
<li><strong>Anyone relying on a failed template answering <code>404</code>/<code>502</code></strong>: a response/forward template that fails, or whose output isn't valid, now answers <code>500</code> by default (<code>templateFailureAsServerError</code>); set it to <code>false</code> to keep the 8.0.0 answers.</li>
</ul>
<p>Also worth checking, though none is a breaking change: if you override the standard Docker images' <code>ENTRYPOINT</code> or copy the jar out of them, <code>/mockserver-netty-jar-with-dependencies.jar</code> is now split into <code>/mockserver.jar</code> and <code>/mockserver-deps.jar</code> — use <code>-cp /mockserver.jar:/mockserver-deps.jar:/libs/*</code> (<code>java -jar /mockserver.jar</code> still runs, but without the CDS start-up archive, so it starts more slowly); with <code>forwardProxyBlockPrivateNetworks</code> on, a request that matches no expectation and whose <code>Host</code> header names MockServer itself by a name it doesn't recognise as its own (a Docker Compose or Kubernetes service name, for example) now gets <code>502 Bad Gateway</code> instead of <code>404 Not Found</code>, because that name resolves to a private address — add the name to <code>noProxyHosts</code>, or set <code>attemptToProxyIfNoMatchingExpectation=false</code> if MockServer isn't us
ed as a proxy, to get the <code>404</code> back; and if you set <code>localBoundIP</code>, it now also keeps the DNS and HTTP/3 ports on that address — a DNS query or HTTP/3 request sent to another address of the host is no longer answered, so send them to the <code>localBoundIP</code> address, or leave <code>localBoundIP</code> unset.</p>
<!-- raw HTML omitted -->
</blockquote>
<p>... (truncated)</p>
</details>
<details>
<summary>Changelog</summary>
<p><em>Sourced from <a href="https://github.com/mock-server/mockserver-monorepo/blob/master/changelog.md">org.mock-server:mockserver-core's changelog</a>.</em></p>
<blockquote>
<h2>[9.0.0] - 2026-10-15</h2>
<p>This release delivers a sustained performance and memory programme alongside data-integrity fixes under load, plus a large set of LLM-provider correctness fixes, dashboard improvements, and client-library parity work. Headline numbers from the single-load-generator benchmark on the same six-core rig (builds 420 and 464): the healthy ceiling rises from 39,033 to 57,149 req/s and the peak from 43,671 to 59,905 req/s, with p95 at 32,000 req/s falling from 56.6 ms to 0.44 ms on the new ZGC default in the Docker images; event-log retained heap at 20,000 entries falls from 429 MB to 61 MB; Docker image download shrinks ~23%; and instance shutdown drops from ~107 ms to near zero. 22 BREAKING changes affect HTTP/3, DNS mocking, binary (non-HTTP) proxying and binary expectation matching while proxying, template-failure response codes, <code>maxLoggedMatchFailures</code>'s default, initialisation-file <code>id</code> conflicts, the Node client's TypeScript typings and <code>exports</code
> map, <code>LOG_ENTRIES</code> log output, control-plane error handling and mTLS, the Rust client's enums, verification-failure wording, response <code>statusCode</code> validation, AsyncAPI and response/OpenAPI verification, GenAI trace span names, the Node client's recorded-request typings, and the Go client/Testcontainers module's <code>/v9</code> module paths — see <em>Upgrading from 8.0.0</em> and the <code>BREAKING</code> entries under <em>Changed</em>. For a per-change migration list, see the upgrade guide at <a href="https://www.mock-server.com/mock_server/upgrading_to_9.html">https://www.mock-server.com/mock_server/upgrading_to_9.html</a>.</p>
<table>
<thead>
<tr>
<th>Metric</th>
<th>Before</th>
<th>After</th>
</tr>
</thead>
<tbody>
<tr>
<td>Throughput, healthy ceiling / peak (req/s, 6 cores)</td>
<td>39,033 / 43,671</td>
<td>57,149 / 59,905</td>
</tr>
<tr>
<td>p95 latency at 32,000 / 48,000 req/s offered</td>
<td>56.6 ms / 82.4 ms</td>
<td>0.44 ms / 12.0 ms</td>
</tr>
<tr>
<td>Event-log heap (20,000 entries)</td>
<td>429 MB</td>
<td>61 MB</td>
</tr>
<tr>
<td>Docker image download (linux/arm64, standard image)</td>
<td>~167 MB</td>
<td>~129 MB</td>
</tr>
<tr>
<td>Instance shutdown time</td>
<td>~107 ms</td>
<td>~0 ms</td>
</tr>
</tbody>
</table>
<p>"Before" is perf build 420 (commit d568695a2, 2026-09-24, JDK 17.0.20, G1 collector), measured nine days after the 8.0.0 tag and already carrying some of this release's own work, since 8.0.0 itself was never measured on this rig. "After" is perf build 464 (commit efdc5227b2, 2026-09-27, JDK 25, ZGC), the performance page's single-load-generator figures; the page's headline is now a different, multi-generator measurement (see <em>Changed</em>). Both are comparable with each other but not with any benchmark published after this release.</p>
</blockquote>
</details>
<details>
<summary>Commits</summary>
<ul>
<li><a href="https://github.com/mock-server/mockserver-monorepo/commit/e423b4641dfc6530df10cafbf1bf37eb5638b557"><code>e423b46</code></a> release: set version 9.0.0</li>
<li><a href="https://github.com/mock-server/mockserver-monorepo/commit/2d9f1681ec23184d32bf5bd46ec7e99f0bfd3eb9"><code>2d9f168</code></a> fix(release): unblock -DskipTests builds, dry-runs and the cosign probe</li>
<li><a href="https://github.com/mock-server/mockserver-monorepo/commit/043260e03d2cbf8bae081742e56e94bd21fd231f"><code>043260e</code></a> build(deps): bump <code>@tanstack/react-virtual</code></li>
<li><a href="https://github.com/mock-server/mockserver-monorepo/commit/6882f527b6d178a4847df31cfbe09d9cb5207d85"><code>6882f52</code></a> docs(plans): record the Go example-digest fix needed before 10.0.0</li>
<li><a href="https://github.com/mock-server/mockserver-monorepo/commit/1913a0d9ecbffecf12e348f5a87688956415be3e"><code>1913a0d</code></a> docs(changelog): consolidate the 9.0.0 release notes</li>
<li><a href="https://github.com/mock-server/mockserver-monorepo/commit/259230452021dee8144c4f7eb5c72efb075d93d6"><code>2592304</code></a> fix(core): complete a tunnelled relay connect after the codec is gone</li>
<li><a href="https://github.com/mock-server/mockserver-monorepo/commit/92ccf9e8667373b4d6665cc776884dc1f50c7921"><code>92ccf9e</code></a> test(core): hash Go output with the module major as a placeholder</li>
<li><a href="https://github.com/mock-server/mockserver-monorepo/commit/6dfc788f12433ded29fde40a2d983f73df6dd5cc"><code>6dfc788</code></a> docs(website): add the 9.0.0 upgrade guide</li>
<li><a href="https://github.com/mock-server/mockserver-monorepo/commit/779f43f6b1d27430ebc5088e2645900f57948bac"><code>779f43f</code></a> fix(release): keep only marked history out of the release version bump</li>
<li><a href="https://github.com/mock-server/mockserver-monorepo/commit/a8db1d675e9f44ffe48e35c656a89ea0c3dc1b6c"><code>a8db1d6</code></a> docs(release): keep the historical Go /v7 note through the version bump</li>
<li>Additional commits viewable in <a href="https://github.com/mock-server/mockserver-monorepo/compare/mockserver-8.0.0...mockserver-9.0.0">compare view</a></li>
</ul>
</details>
<br />
Updates `org.mock-server:mockserver-client-java` from 8.0.0 to 9.0.0
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`.
[//]: # (dependabot-automerge-start)
[//]: # (dependabot-automerge-end)
---
<details>
<summary>Dependabot commands and options</summary>
<br />
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency
- `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
</details>
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@artemis.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@artemis.apache.org
For additional commands, e-mail: issues-help@artemis.apache.org
Re: [PR] ARTEMIS-X Bump mockserver.version from 8.0.0 to 9.0.0 [artemis]
Posted by "jbertram (via GitHub)" <gi...@apache.org>.
jbertram commented on PR #6806:
URL: https://github.com/apache/artemis/pull/6806#issuecomment-6258895853
Superseded by https://github.com/apache/artemis/pull/6811 with Jira reference ARTEMIS-6198.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@artemis.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@artemis.apache.org
For additional commands, e-mail: issues-help@artemis.apache.org
Re: [PR] ARTEMIS-X Bump mockserver.version from 8.0.0 to 9.0.0 [artemis]
Posted by "jbertram (via GitHub)" <gi...@apache.org>.
jbertram closed pull request #6806: ARTEMIS-X Bump mockserver.version from 8.0.0 to 9.0.0
URL: https://github.com/apache/artemis/pull/6806
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@artemis.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@artemis.apache.org
For additional commands, e-mail: issues-help@artemis.apache.org
Re: [PR] ARTEMIS-X Bump mockserver.version from 8.0.0 to 9.0.0 [artemis]
Posted by "dependabot[bot] (via GitHub)" <gi...@apache.org>.
dependabot[bot] commented on PR #6806:
URL: https://github.com/apache/artemis/pull/6806#issuecomment-6258896466
OK, I won't notify you again about this release, but will get in touch when a new version is available. You can also ignore all major, minor, or patch releases for a dependency by adding an [`ignore` condition](https://docs.github.com/en/code-security/supply-chain-security/configuration-options-for-dependency-updates#ignore) with the desired `update_types` to your config file.
If you change your mind, just re-open this PR and I'll resolve any conflicts on it.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: issues-unsubscribe@artemis.apache.org
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@artemis.apache.org
For additional commands, e-mail: issues-help@artemis.apache.org