Skip to content

Releases: jbwheatley/pact4s

v0.8.0

07 Dec 12:36
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v0.7.0...v0.8.0

v0.7.0-java8

24 Nov 15:53
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.6.0-java8...v0.7.0-java8

v0.7.0

24 Nov 15:54
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.6.0...v0.7.0

v0.6.0-java8

31 Oct 16:38
Compare
Choose a tag to compare

What's Changed

New Contributors

Full Changelog: v0.0.19...v0.6.0-java8

v0.6.0

31 Oct 16:38
Compare
Choose a tag to compare

What's Changed

Full Changelog: v0.5.1...v0.6.0

v0.5.0

30 Aug 09:57
Compare
Choose a tag to compare

equivalent java 8 version is v0.5.0-java8

What's Changed

Full Changelog: v0.4.1...v0.5.0

v0.4.0

28 Jun 16:03
Compare
Choose a tag to compare

This is the first release that targets scala 3. This has been a long time coming - I first tried this in April 2021 using 3.0.0-RC2 and discovered this compiler bug that prevented moving forward: scala/scala3#12086
This has now been fixed in 3.1.3!

As usual, the java8 compatible version is available as 0.4.0-java8.

v0.3.1

27 May 08:44
Compare
Choose a tag to compare

Fixes issue with provider state callbacks not inserting parameters into requests. issues #197 #122, fixed in #200 @jbwheatley

0.3.0

15 Apr 10:48
Compare
Choose a tag to compare

This version should be source compatible with 0.2.0. Apart from version updates, in this release:

  • #176 changed how data classes are defined internally and added additional convenient to use constructors for many of the models.
  • #181 addressed an issue with pact forging. pact-jvm will not write pacts to a file if not all interactions have been registered by the mock server - e.g. if you don't have a test for each interaction. This error is now surfaced to the user and will cause the forger suite to fail if not all interactions are tested.

What's Changed

Full Changelog: v0.2.0...v0.3.0

v0.2.0

26 Feb 20:35
Compare
Choose a tag to compare
  • Added support for branches in consumer version selectors - see #89

Added the following methods on ConsumerVersionSelector to facilitate these additions:

ConsumerVersionSelector().
  withBranch(Branch("foo")) 

For convenience we include Branch.MAIN and Branch.MASTER for main and master resp.

ConsumerVersionSelector().
  withMainBranch(true)
ConsumerVersionSelector().
  withMatchingBranch(true) //gets pacts with branch that is the same as the current branch name. 
  • Added support for consumer version selectors for deployed and released versions - see #68

As the selectors in this issue are subject to change, and more may be made available to the broker in the future, additional selectors such as these can be provided with the following method on ConsumerVersionSelector:

ConsumerVersionSelector().
  withAdditionalSelectors(Map("deployed" -> true, "environment" -> "stg"))
  • Added support for publishing verification results with a branch - see #87
    When verifying pacts, the argument publishVerificationResults provided to the test function verifyPacts can be modified to specify the branch that will be associated with the verification results when they are published:
verifyPacts(
  publishVerificationResults = Some(
    PublishVerificationResults(
      providerVersion = "ABC",
      branch = Branch("feature/x")
    )
  )
)
  • Added apply method for ProviderInfoBuilder apply(name: String, providerUrl: URL, pactSource: PactSource) that takes a URL