Release - 4.1.39 New release published by rholshausen Back-ported fixes and consumer version selectors from v4.3.x • d7fccb6 - fix(Gradle): fixes gradle provider verification from pact file #1587 • 77b79a2 - fix(Gradle): Update methods on GradleProviderInfo to support calling hasPactsFromPactBroker without options #1586 • 14a5143 - fix: for NoSuchMethodError: void kotlin.jvm.internal.FunctionReferenceImpl • 05dce3c - feat: Update Maven plugin readme with latest consumer version selectors • 34d19e3 - feat: Update Maven plugin with latest consumer version selectors • 7177bdc - chore: remove deprecation annotation from selector tag methods • 1a51957 - fix: annotation check was failing on JDK8 • d23fcbe - refactor: rename ConsumerVersionSelectors annotation so it does not clash with the model class • 17e51e3 - refactor: Consumer Version Selectors method does not need a parameter • 743ac4b - Feat: Support consumer version selectors DSL for JUnit 5 • f54ee01 - feat(JUnit): allow pact loader to setup from the test class instead of just annotations • afeca40 - chore: correct the GitHub URL in Gradle plugin • 957f3a3 - chore: upgrade Gradle project to use 1.0 of the plugin-publish plugin • f021ef1 - feat: add Gradle DSL functions for deprecated tag forms of selectors • fe643c9 - fix: call the updated selector method from the Gradle plugin • 0afc954 - Feat: Implement new Gradle DSL for consumer version selectors • 01e45dc - feat: allow consumer version selector JSON to be provided with an environment variable • 57533e3 - Update gradle.properties to fix Vulnerability • 33d659e - Added secondary constructor to FormPostBuilder to facilitate passing a ContentType. • 8a6095c - chore: correct offset expressions in date-time expressions • a36ce77 - chore: correct message on warning log entry • e0b15ab - Update PactCanIDeployTask.groovy • 1a80e41 - Adding support for Kafka Schema Registry JSON messages. Do not store magic bytes in broker: - use the content-type to add them to messages for Consumer Tests - remove first 5 bytes from provider tests before parsing as JSON • b48e37d - feat: Add support for PactLoader path value expressions • 270808a - Adding support for Kafka Schema Registry JSON messages. Utilise the Content-Type to indicate KSR messages. Deal with the 5 "magic" bytes at the start of the JSON. • 8dc11bd - fix: make the use of content type overrides consistent #1569 • 1f2cf91 - docs: link to 'Using provider states effectively' • 3e09e6c - feat: allow consumer version selector JSON to be provided with an environment variable • bec44aa - fix: make the use of content type overrides consistent #1569 pact-foundation/pact-jvm

Is this the appropriate version to use for a java 8 project using Junit5?

You probably need to tag someone @MiKey 😉

Not usually, but in this case maybe

What’s the TL;DR? We are using: •

au.com.dius.pact:consumer:4.1.39

•

au.com.dius.pact:provider:4.1.39

• On a Java 8 app • Using Pactflow The problem is, when running provider verification, we get a no pacts found exception. Tomorrow I can post more details from setting breakpoints in the pact libraries.

Jake is the right person to ask not me, I believe it's more of an error from the PactBroker code in CI that can't find the system vars that define where the broker is…different errors locally vs CI

That is the correct version to use with JDK 8

Thanks @uglyog - we’ll dig in more and try to find more details on the failure here.