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