Releases: pact-foundation/pact-jvm
Releases · pact-foundation/pact-jvm
4.5.8
Maintenance Release
- 6aec655 - feat(compatibility-suite): Implemented Synchronous Messages feature
- c44b05a - feat(compatibility-suite): Add V4 message scenarios
- aeb09e9 - fix(compatibility-suite): Correct error messages to be consistent
- c37387f - chore(compatibility-suite): Implement V4 matching rule and generator scenarios
- 73c6adb - chore: Add additional logging to matchContentType
- c1964a1 - feat(compatibility-suite): Implement initial V4 features
- 894016d - feat(compatibility-suite): Implemented V3 message provider feature
- 5751c1f - feat(compatibility-suite): Implement steps for V3 message consumer
- bce3543 - fix(compatibility-suite): header values can have optional spaces
- bd2f380 - feat: Add sys prop to set default Pact spec version; deprecate PactSpecVersion.UNSPECIFIED #1705
- 52cb552 - fix: Pact parser is removing quoting on Content-Type params #1538
- 6c1f850 - chore: Update error messages to match the compatibility-suite
- 3e22d63 - upgrade to kotlin-logging 5 (oshai)
- cdf6d2c - feat(compatibility-suite): Add V3 HTTP generator scenarios
- 308a7f7 - chore: DateTimeGeneratorSpec could fail on millisecond boundaries (Ronald Holshausen, Fri Jul 21 09:43:33 2023 +1000)
- 3cc5e9b - chore: TimeGeneratorSpec could fail on millisecond boundaries
- bf66443 - feat(compatibility-suite): Implement V3 matching rule and generator scenarios
- 88c023f - feat(compatibility-suite): Implemented V3 features
- 31004ad - feat(compatibility-suite): Implemented remaining V1 scenarios
- 27498a1 - feat(compatibility-suite): Implemented scenarios related to multipart bodies
- af661f3 - feat(compatibility-suite): Implemented scenarios related to non-JSON bodies
- 68b8822 - feat: Correct the matching rules to match the latest compatibility-suite
- 9097226 - feat(V4): Add a JUnit 4 test using the status code matcher
- 3af6b08 - fix: Update RestPactRunner and MessagePactRunner to support V4 Pacts #1692
- a6b6e83 - feat(compatibility-suite): Implemented steps for V2 matching rule scenarios
- f0a4f6c - fix: Matching rules were not being applied to repeated header values
- 28d544e - fix: Matching rules were not being applied to repeated query parameters
- e272dc2 - feat(compatibility-suite): Implemented V1 scenarios for verifying different HTTP response parts
- 474ab17 - fix: Do not print out multipart bodies as they could have binary parts
- 8e60638 - chore: Update build to support Gradle 8
- 26bc5e9 - feat: Add steps for initial V2 HTTP compatibility scenarios
4.1.42
Back-ported fixes from v4.2.x
- 038669b - fix: Replace com.github.zafarkhaja.semver.Version with a local version parser
- d390ce8 - refactor: converted the remaining Java DSL body classes to Kotlin
- 9677c8f - refactor: converted PactDslJsonBody to Kotlin
- b3fc7a5 - refactor: converted PactDslJsonArray to Kotlin
- 367d332 - refactor: converted DslPart to Kotlin
- 56dc42d - chore: Minor dependency upgrade
- a73b2f4 - chore: Upgrade Groovy to 3.0.18
- 04f4d5c - fix: Pact parser is removing quoting on Content-Type params #1538
- 313be5c - chore: Upgrade Gradle to 6.9.4
4.6.1
4.6.1
- abf5fb8 - fix: EachValue matcher was applying the associated rule to the list and not the items in the list
- a2f7fbf - fix: Support string escape sequences in matching definitions
- 0cd9ad0 - feat: Implemented scenarios for no provider state callback configured + request filters
- fdea11e - feat: Add builder interface for plugins to provide DSL to construct interactions
- 0f5dc41 - feat: Call provider state callbacks with empty state when there is no state defined
- 7e8d7fc - fix: MockServerURLGenerator was not combining URL fragments correctly
- b369fec - feat: got the remaining V1 HTTP provider scenarios passing
- b7b2a12 - feat: Implemented initial V1 HTTP provider specs in compatibility suite
- a0a5a96 - use valid module name in manifest
- dbc59a4 - feat: Implement the remaining V1 HTTP consumer scenarios
- e4eab7b - feat: Implement initial compatibility suite feature for V1/HTTP interactions
- fa65ca2 - Allow to set the port via an expression. (holomekc)
- 9f5aa17 - Merge branch 'master' into v4.6.x
4.5.7
Bugfix Release
- abf5fb8 - fix: EachValue matcher was applying the associated rule to the list and not the items in the list
- a2f7fbf - fix: Support string escape sequences in matching definitions
- 0cd9ad0 - feat: Implemented scenarios for no provider state callback configured + request filters
- fdea11e - feat: Add builder interface for plugins to provide DSL to construct interactions
- 7c41fc1 - feat: implement compatibility suite provider state steps
- 0f5dc41 - feat: Call provider state callbacks with empty state when there is no state defined
- 7e8d7fc - fix: MockServerURLGenerator was not combining URL fragments correctly
- b7b2a12 - feat: Implemented initial V1 HTTP provider specs in compatibility suite
- a0a5a96 - use valid module name in manifest (Daniel Heinrich)
- dbc59a4 - feat: Implement the remaining V1 HTTP consumer scenarios
- e4eab7b - feat: Implement initial compatibility suite feature for V1/HTTP interactions
- fa65ca2 - Allow to set the port via an expression. (holomekc)
- 1819fcf - chore: add or and orElse to Result class
- d3dbc52 - Use shorthand annotation instead of @ExtendWith (Holly Cummins)
Contributors
ExtendWith
Assets 2
4.6.0
Kotlin 1.8 + JDK 17 release
- f5aff82 - chore: Upgrade dependencies
- 1fafbf4 - chore: Upgrade Kotlin to 1.8.21, KTor to 2.3, plugin driver to 0.4.0
- d3dbc52 - Use shorthand annotation instead of @ExtendWith (Holly Cummins)
Contributors
ExtendWith
Assets 2
4.5.6
Bugfix Release
- 3f4d0f3 - chore: Upgrade Groovy to 4.0.11
- 2070ce5 - fix(JUnit5): Provider name can be provided with the @Pact annotation #1684
- 8a70a1a - fix(JUnit5): IllegalStateException was being raised when multiple Pacts were configured for the same provider #1457
- 9aebbb5 - fix(JUnit5): do not overwrite class level provider name is the method one is empty
Contributors
Pact