Hi, we're using Pact Spring6/Springboot3 + JUnit5 Support for our Spring Pact Verification tests and our self hosted Pact broker uses a self signed certificate. To allow the tests to interact with the broker we're setting JVM system properties (

<http://javax.net|javax.net>.ssl.trustStore

and

<http://javax.net|javax.net>.ssl.trustStorePassword

) for the trust store and password. Is this the recommended approach for this or is there another better way we can configure the http client used to interact with the Pact broker?

Please see these instructions on running and accessing a Pact Broker over TLS https://docs.pact.io/pact_broker/advanced_topics/using-tls/

@Elson Ho has left the channel

Hi, my team has a library for reusing common code across our microservices. One of the modules is a http client for interacting with a service named

foo

. We have written consumer contract tests within this module, however, I’m not sure where to go from here. We could publish the pacts to the broker but that would just prevent the module from going out of sync with

foo

. We don’t record deployments of the module because it isn’t a service. So this wouldn’t help to prevent the services from going out of sync with

foo

. What we actually want to do is publish pacts for multiple services, services who happen to be using the module, to prevent them from going out of sync with the

foo

service. I’m not sure where we’re going wrong so any help would be greatly appreciated. Thanks 🙂

Hi Team, I have a couple of questions regarding the behavior and configuration of Work In Progress (WIP) pacts. 1. In a scenario where the WIP feature is enabled and a new contract is published to a WIP branch, but the provider hasn’t yet implemented the expected state or supported the feature, the provider pipeline won’t fail due to pending pacts being enabled. However, if the consumer pipeline includes a

can-i-deploy

step to check verification status—will this step fail, or still pass? 2. Also, according to the documentation, enabling WIP pacts initially seemed to require no changes on the provider side. However, I noticed that the

includeWipPactsSince

property is mentioned as part of the provider verification configuration to include modified pacts. Could someone clarify whether this property is mandatory for enabling WIP pacts on the consumer? Appreciate your insights!

Release - 4.6.18 New release published by rholshausen ## Maintenance Release • 8a1e8b0 - chore: fix port conflict in test • 8c22c52 - chore: Update release process to use jreleaser • 57c5bda - fix: add Lambda DSL methods that are the same as the old DSL arrayEachLike #1877 • 0122422 - chore: Update provider dependencies • ab81b32 - chore: Update core dependencies • f3b1d6e - chore: Update consumer dependencies • 87cc6c0 - chore: Update main dependency versions • 8696796 - chore: Update Gradle to 7.6.6 • 897aaea - Reference Quarkus in service providers section (Holly Cummins) • c50f627 - chore(deps): bump actions/setup-java from 3 to 5 • 4670fa8 - Correct Java versions in developer-facing content (Holly Cummins) • aa17dca - Update classgraph to work around compatibility issue (Holly Cummins) • 286861e - chore(CI): update to actions/cache@v4 • 64a9312 - chore: Update plugin driver to 0.5.2 • 7a924a0 - fix: Ensure provider state is injected when verifying synchronous message pacts (Ruud Welling) pact-foundation/pact-jvm

Release - 4.7.0-beta.2 New release published by rholshausen ## Maintenance Release • 89bdf49 - chore: Upgrade Kotlin to 2.2.21 • 67c4a96 - chore: Correct some deprecation warnings • 0c727fe - chore: Correct release script • 8a1e8b0 - chore: fix port conflict in test • 8c22c52 - chore: Update release process to use jreleaser • 57c5bda - fix: add Lambda DSL methods that are the same as the old DSL arrayEachLike #1877 • 0122422 - chore: Update provider dependencies • ab81b32 - chore: Update core dependencies • f3b1d6e - chore: Update consumer dependencies • 87cc6c0 - chore: Update main dependency versions • 897aaea - Reference Quarkus in service providers section (Holly Cummins) • c50f627 - chore(deps): bump actions/setup-java from 3 to 5 • 4670fa8 - Correct Java versions in developer-facing content (Holly Cummins) • aa17dca - Update classgraph to work around compatibility issue (Holly Cummins) • 5b8f441 - chore(v2-matching-engine): Fixes ported from Pact-Rust ( • 7591a7f - chore: V4 response specification tests were not being run • b2517d2 - chore: V4 response specification tests were not being run • 6054d6a - chore(v2-matching-engine): Cleanup unused code • f20aaa5 - chore: Add V2 engine build to CI • 7876f6c - chore: Fix test after merge from feat/v2-matching-engine • 98febe1 - chore(v2-matching-engine): Support content type matcher at body root • 6b8bce2 - chore(v2-matching-engine): Fixes to get existing tests passing • ca19744 - chore(v2-matching-engine): Implemented 'and' and 'or' actions • 14aef70 - chore(v2-matching-engine): Enable XML plan builder and correct spec tests • 13825e5 - chore(v2-matching-engine): Fix DocPath.dropMarkers to inject a zero index for markers • e200f1f - chore(v2-matching-engine): Fix for JSON array items which were missing error else clause • 55780da - chore(v2-matching-engine): Fix for-each statement with JSON arrays • 5865889 - chore(v2-matching-engine): Fix the compatability suite • b855c06 - chore(v2-matching-engine): Enable V2 matching engine with PACT_MATCHING_ENGINE=v2 • 03b0d41 - chore(v2-matching-engine): Support matching rules with XML • 537eb91 - chore(v2-matching-engine): Support matching rules with XML • 6eacce6 - chore(v2-matching-engine): Exclude carriage returns from rendered XML • b474476 - chore(v2-matching-engine): Fix build failures • 98fad09 - chore(v2-matching-engine): Support matching XML attributes • 672919b - chore(v2-matching-engine): Support very basic XML • 0200bda - chore(v2-matching-engine): Implement basic XML plans • 8efe1ca - chore(v2-matching-engine): Fix static code violations • ff884f0 - chore(v2-matching-engine): Implemented matching query parameters • 093e928 - chore(v2-matching-engine): Implemented final parts of matching headers • 8df137d - chore(v2-matching-engine): Fix static code violations • 1e63c79 - chore(v2-matching-engine): Support matching headers with number type matchers • c770f4c - chore(v2-matching-engine): Support matching headers with multiple values • a84fe31 - chore(v2-matching-engine): Support matching rules with headers • 52f54fd - chore(v2-matching-engine): Errors need to be escaped in the plan output • a534ffd - chore(v2-matching-engine): Implemented basic matching of headers • 74c8e69 - chore(v2-matching-engine): Implemented support for matching rules with paths • 0fc3f6f - chore(v2-matching-engine): Got simple JSON matching test passing • d17fb50 - feat(JUnit5): Add tests to cover the changes <https://github.com/pact-foundation/pact-… pact-foundation/pact-jvm

Hey there, how do i implement sync & async provider tests (so REST and event based messaging) for the same provider? Currently we get "No test target has been configured for AsynchronousMessage interactions" in the REST Provider Test class. Do we need to set a filter for this class or something?

Release - 4.7.0-beta.3 New release published by rholshausen ## Support for Spring 7 and Spring Boot 4 • f0e01e8 - Add new module to support Spring 7 and Spring Boot 4 (Martin Schmidt) pact-foundation/pact-jvm

@rholshausen au.com.dius.pact.provider:spring7 is not available at maven central yet. How can I use it? It is working. My bad.

Release - 4.6.19 New release published by rholshausen ## Maintenance Release • ce88f27 - Move custom-mimetypes.xml directly to classpath (Carolyn Biggar) • afb1cff - [broken build] Change expected supertype for application/json to text/javascript (Carolyn Biggar) • 12029d5 - [broken build] Upgrade tika-core 2.9.4 > 3.2.3 (Carolyn Biggar) • 076c6cc - Update Kotlin version for 4.7.x in README pact-foundation/pact-jvm

Release - 4.6.20 New release published by rholshausen ## Small Feature Release • 5caa7c5 - feat: Add a JUnit 5 filter by interation type #1894 • 698a93b - chore: switch from org.apache.commons:commons-io to commons-io:commons-io #1878 • bb1b857 - fix: Support message tests where the annotated method is on a parent class #1890 • 9d97753 - feat: Add support for using BodyBuilder implementations with MessageContentsBuilder pact-foundation/pact-jvm

Release - 4.7.0-beta.4 New release published by rholshausen ## Support Gradle 9+/JVM, removed deprecated methods, other small feature enhancements • 6db476b - fix: Switch from the use of URL to URI in Gradle plugin to support Gradle 9+/JVM 25 #1892 • 5bfd06d - feat: Add a JUnit 5 filter by interation type #1894 • b7f76e2 - chore: Fix test after upgrade to Apache Tika • 698a93b - chore: switch from org.apache.commons:commons-io to commons-io:commons-io #1878 • bb1b857 - fix: Support message tests where the annotated method is on a parent class #1890 • 798d709 - fix: fix ClassCastException for multipart requests in Spring7MockMvcTestTarget (Stefan Kranich) • 9d97753 - feat: Add support for using BodyBuilder implementations with MessageContentsBuilder • da16f81 - chore: Update use of deprecated DateFormatUtils ISO_8601 constants • 859051b - chore: remove deprecated displayFailures method • 02c639b - core: Remove the deprecated pactFileAuthentication property • 0b30ac2 - core: Remove the deprecated pactFileAuthentication property • 1530ce4 - chore: Upgrade Kotlin to 2.3.0 • 31054d7 - chore: Remove deprected cookie() and contentType() functions and PactFolder annotation • b9f2b2b - chore: Remove deprected DSL.matcherKey method • d794f01 - chore: Remove deprecated ProviderInfo.mockServerImplementation property • 6c99423 - chore: Deprecate interaction conflictsWith method and remove ignored tests • 85b71b4 - chore: Fix Gradle deprecation warnings • 58ec629 - chore: Upgrade Gradle to 8.12.1 • ce88f27 - Move custom-mimetypes.xml directly to classpath (Carolyn Biggar) • afb1cff - [broken build] Change expected supertype for application/json to text/javascript (Carolyn Biggar) • 12029d5 - [broken build] Upgrade tika-core 2.9.4 > 3.2.3 (Carolyn Biggar) • 076c6cc - Update Kotlin version for 4.7.x in README pact-foundation/pact-jvm

Hi all, I tried to use below code

@ExtendWith(SpringExtension.class)
@SpringBootTest(webEnvironment = SpringBootTest.WebEnvironment.DEFINED_PORT)
@Provider("provider-name")
@AllowOverridePactUrl
@PactBroker(scheme = "https", host = "${PACT_BROKER_BASE_URL}",providerBranch = "main", authentication = @PactBrokerAuth(token = "${PACT_BROKER_TOKEN}"))
public class ProviderVerificationTest

I exported my url and token to env variables. When running that test I'm getting

[ERROR]   ProviderVerificationTest.pactVerificationTestTemplate(PactVerificationContext) » IllegalArgument Invalid pact broker host specified ('${PACT_BROKER_BASE_URL}'). Please provide a valid host or specify the system property 'pactbroker.host'.

any idea what may be wrong in my env/configuration?

Hi team, another question. I'm using PactFlow (PactBroker) and after running some unit tests for my provider (not the ProviderVerificationTest) I have multiple test results files from my JUnit tests(~10 files). It is possible to upload only 1 file using

pactflow publish-provider-contract

. Did you faced such case before? How do you handle that?

Hi Team, There is consumer provider pair in the pact broker (prod). Both services are doing the contract testing for very long and both were compatible with contract. So provider team has reported that they are getting this exception while verification is happening. Since verification is happening through CI/CD pipeline. Exception : pactVerificationTestTemplate(PactVerificationContext) > initializationError FAILED au.com.dius.pact.provider.junitsupport.loader.NoPactsFoundException: No Pact files were found to verify Provider: LossPrevention Consumer: TSAYS Source: Pact Broker https://prod-pact-broker-url. Issue is getting fix when consumer is publishing the result back again over pact broker, without making any change in the provider test case. Note : Provider is not using consumerVersionSelector feature in the provider test case. Tried to replicate but not able to replicate.

Hi 👋 How can I use Pact JVM to verify that a provider serialize a JSON that conform with a pact file? Just like this the example on Pact Net https://docs.pact.io/implementation_guides/net/docs/messaging-pacts#provider-tests.

@Norbert Gulácsi has left the channel

Hi 👋 Why does Pact stop publishing to Maven Central? I tried to adopt Pact JVM in my organization and this posed some concerns among our engineers.

Release - 4.7.0-beta.5 New release published by rholshausen Bugfix Release • fff39e5 - fix: HttpHeaders.containsKey() which was removed in Spring Framework 7, causing NoSuchMethodError at runtime #1902 • f27d9aa - fix: Switch from the use of URL to URI in Gradle plugin to support Gradle 9+/JVM 25 #1892 • 161c083 - Revert "fix: Switch from the use of URL to URI in Gradle plugin to support Gradle 9+/JVM 25 #1892" pact-foundation/pact-jvm

Release - 4.7.0-beta.6 New release published by rholshausen Maintenance Release • 698c1b2 - chore: Update readme after upgrading Kotlin to 2.3.10 • 0a98346 - chore: Upgrade Kotlin to 2.3.10 • e9f112a - feat: add support for custom headers with the PactBroker annotation #1835 • f0283de - feat(consumer): Make the mock server log entries for requests and responses clearer in the log output • bdb9db1 - chore(consumer): Add test for MockServerLog • 7cf4acc - feat(consumer): Make the mock server log entries for requests and responses clearer in the log output • 451d7f0 - fix: Replace Generex with a custom random string generator #1848 • 5caa7c5 - feat: Add a JUnit 5 filter by interation type #1894 pact-foundation/pact-jvm

Release - 4.7.0 New release published by rholshausen 4.7.0 Release • 00a5028 - chore: remove beta flag from 4.7.x version • 95af913 - chore: Update supported JDK versions table • 1a684e1 - chore: Correct the doctests for line endings on Windows • 468b9a3 - chore: Add doctests for consumer and consumer/junit5 • 12e3c37 - chore: Add Gradle task to generate tests off readme code blocks • 119efb3 - feat: Check for

@Ignore

on the Pact method in the post spec check stage • 6293508 - chore: Update main readme • 06deeb5 - feat: Check for the mock server field and raise an exception if it is missing • d39f691 - feat: rename annotation so it does not have the same name as the JUnit one • 977572c - feat: Add a consumer spock module pact-foundation/pact-jvm

Release - 4.7.1 New release published by rholshausen Feature release • 0cdd0e3 - chore: Corrected all the doctests after update to the readmes • a34e72a - chore: Add TOC to the consumer and provider readmes • f695f6d - feat: Update readmes with details on using external references • 3cb5eb5 - feat: Display references in the verifier output • 170b276 - feat: Add a method to the DSL interaction builders to capture external references • b43d225 - feat: Add a method V4Interaction to capture external references • 130aaa2 - chore: Add tests for V4Interaction and child classes • 4ee8ddd - chore: fix typo breaking internal build (Kevin Rohan Vaz) • 76cabe4 - feat: Add doctests for the readme code blocks #1352 • e2ee20b - feat: Add a Kotlin consumer DSL #1352 • 39c734a - feat: add arrayContains as a matching rule expression • 2de7c50 - refactor: deduplicate write logic in MERGE branch (biergit) • 332f3b3 - fix: write through RandomAccessFile instead of opening a competing file handle (biergit) • 66e25c3 - Refactor writePact to handle empty pactFile case (biergit) pact-foundation/pact-jvm

Release - 4.5.14 New release published by rholshausen Maintenance Release • a5b3754 - chore: fix for failing CI build • 741e9f7 - chore: Update release process to use jreleaser • 604bffc - chore: Fix CI build • f803789 - Fix deprecated GitHub Actions versions in compatibility-suite workflow • 8301136 - chore: Fix CI build • 1c877e1 - chore: Remove 4.1.x from the supported versions • 0611770 - chore: add pact-jvm user agent (JP-Ellis) pact-foundation/pact-jvm

Release - 4.6.21 New release published by rholshausen Maintenance Release • 71a5907 - chore: fix jreleaser config for Maven Central deployment • 22c5ce3 - chore: fix release script • 2bfc9ca - chore: fix jrelease • 0d74d02 - Fix deprecated GitHub Actions versions in compatibility-suite workflow • d16a2f7 - chore: Fix CI build • 28cfd65 - chore: Remove 4.1.x from the supported versions • 2894372 - chore: add pact-jvm user agent (JP-Ellis) • 6d4c199 - docs: update docs for docusaurus upgrade (Kevin Rohan Vaz) pact-foundation/pact-jvm

Release - 4.7.2 New release published by rholshausen Maintenance Release • 33a4e60 - chore: fix jreleaser config for Maven Central deployment • ae62862 - chore: fix release script • 05df599 - chore: fix jrelease • 07cadd6 - Fix deprecated GitHub Actions versions in compatibility-suite workflow • a796b1c - fix: update deprecated GitHub Actions versions in gradle.yml • a1ebba0 - chore: Remove 4.1.x from the supported versions • 2926d7f - chore: add pact-jvm user agent (JP-Ellis) • 34848ae - fix: include insecureTLS in options map so PactReader honours it when loading pacts (#1917) • a5ea6c6 - chore: update Pact plugin driver to version supporting initial V2 plugins • f3aec45 - chore: buffer JSON reader source • 373756a - chore: optimize JSON parser object key parsing • 3021c0e - chore: add JMH benchmarks for JSON parser • 31d29cd - preformance(v2-engine): Make DocPath expr field lazy so it is not calculated in the constructor • 127e22d - chore(matchers): Add JMH benchmark harness for the V2 matching engine • 6914885 - chore: Fix static code violations • 42d6d76 - feat(v2-engine): Add multipart/form-data support to V2 matching engine • e2ef70f - fix(v2-engine): Port 4 V2 engine fixes from pact-reference Rust • 5a5a4b3 - chore: Port V2 engine changes from Pact Rust • 75b6fcc - fix(v2-engine): Fix regression where TypeMatcher at root level was incorrectly applied to text body • ca2b86e - fix(v2-engine): Fix remaining 7 XML spec test failures in V2 matching engine • e1f2dbc - fix(v2-engine): Fix spec test failures when running with the V2 matching engine • 41bfe83 - chore: Correct the spec tests to use a header that supports CSV form • 92e5daa - chore: Update the CI pipeline to also run branches • 5f9073c - feat: Implement V2 matching engine for responses • c940065 - chore: cleanup imports #1913 • 19f75f5 - fix: support HttpRequest in no-pacts dummy template (phil.hardwick) • 9d59ad5 - chore(v2-engine): Only split headers where it is known that it is safe to do • 0f9d538 - chore(v2-matching-engine): Implement header:normalize-commas to make it consistent with the Rust V2 engine • 2e72e5b - chore: Correct Gradle plugin jreleaser.yml pact-foundation/pact-jvm

Release - 4.7.3 New release published by rholshausen V2 plugin logging improvements • 368cc3e - chore: Update io.pact.plugin.driver:core to 1.0.0-beta.5 • ee21d6f - feat(008): Set test run ID before plugin calls for log correlation (#1924) pact-foundation/pact-jvm

Release - 4.7.4 New release published by rholshausen Maintenance Release • c5a24aa - chore: Update dependencies • 27748f4 - feat(models): Support matching rules and plugins provided by plugins • acea9dc - chore: Update pact-plugin-driver to 1.2.0 • f2b6966 - feat: register host-provided core content matcher/generator capabilities • 9390503 - chore: Upgrade Kotlin to 2.3.20 • 348ed28 - chore: Update plugin driver to 1.1.0 • e87ccfa - chore: remove beta flag from driver version • 3062902 - chore: add pact-jvm user agent (JP-Ellis) pact-foundation/pact-jvm

Release - 4.7.5 New release published by rholshausen Bugfix Release • 38b575f - fix: Allow Gradle pact file verification without a broker (Matt Van Horn) • 13234ea - chore: Update plugin driver to 1.2.2 • db828e1 - feat(plugins): Pass the generation context and test mode to a plugin generator • 4d26dd8 - feat(plugins): Register the standard matching rules and generators as core plugin capabilities • 42a79e1 - chore(v2-plugins): Support matching rules and generators from plugins • a9fd862 - chore: Update JVM Plugin Driver to 1.2.1 • ef30cd1 - chore: skip publishing pact-jvm-server as it causes Maven Central to return 408 error response pact-foundation/pact-jvm

Hi, I'm getting unexpected end of stream / EOFException: \n not found: limit=0 from the consumer mock server. Java (Spring, not Spring Boot) app, pact-jvm consumer + consumer-junit5, client uses OkHttp 4.12.0. Reproduces on 4.7.3 and 4.6.15, with both KTorServer and JavaHttpServer. Not a DNS/localhost issue either — same result pointing the client at a literal 127.0.0.1:<port>. Fails every single run on both JDK 17 and JDK 25 (100% reproducible, even with -Djava.net.preferIPv4Stack=true). Minimal repro:

@ExtendWith(PactConsumerTestExt.class)
@PactTestFor(providerName = "example-provider", pactVersion = PactSpecVersion.V4)
class ExampleClientPactTest {

    private final OkHttpClient client = new OkHttpClient();

    @Pact(consumer = "example-consumer")
    public V4Pact createOrderPact(PactDslWithProvider builder) {
        return builder
            .given("provider accepts an order")
            .uponReceiving("a request to create an order")
            .path("/orders")
            .method("POST")
            .headers(Map.of("Content-Type", "application/json"))
            .body(new PactDslJsonBody()
                .stringType("customerId", "cust-123")
                .decimalType("amount", 100.00))
            .willRespondWith()
            .status(200)
            .headers(Map.of("Content-Type", "application/json"))
            .body(new PactDslJsonBody()
                .stringType("orderId", "order-456")
                .stringValue("status", "CREATED"))
            .toPact(V4Pact.class);
    }

    @Test
    @PactTestFor(pactMethod = "createOrderPact")
    void should_create_order(MockServer mockServer) throws IOException {
        Request request = new Request.Builder()
            .url(mockServer.getUrl() + "/orders")
            .post(RequestBody.create(
                "{\"customerId\":\"cust-123\",\"amount\":100.00}",
                MediaType.get("application/json")))
            .build();

        try (Response response = client.newCall(request).execute()) {
            assertThat(response.code()).isEqualTo(200);
        }
    }
}

Fails with:

java.io.IOException: unexpected end of stream on <http://localhost>:PORT/...

Caused by: java.io.EOFException: \n not found: limit=0 content=…

at okio.RealBufferedSource.readUtf8LineStrict

at okhttp3.internal.http1.HeadersReader.readLine

at okhttp3.internal.http1.Http1ExchangeCodec.readResponseHeaders

and Pact reports the interaction as not received (client never got a full response). Looks like a race where the client connects before the mock server is ready to respond. Anyone seen this / know a fix or workaround?