1.37.3

We added support for paths that contain colons : in Bi-Directional Contract Testing (BDCT).

We updated the /audit endpoint to support additional query parameters, allowing more flexible filtering of audit events. You can now filter using:

See the updated API documentation.

We updated all dependencies to resolve open CVEs.

We fixed an issue where a SCIM/SAML user that had been deactivated then provisioned again was unable to login.

We fixed an issue with can-i-deploy and bi-directional contract testing, where a V4 Pact with either mixed HTTP and non-HTTP interactions, or only non-HTTP interactions, was incorrectly considered safe to release without a corresponding Pact verification for the non-HTTP interactions.

We fixed an issue with V4 pacts where interaction and message counts were not properly counted.

This release includes time-consuming data migrations related to the V4 Pact fixes described above.

We added a new has_messages boolean field to the pact_versions table. This field is set to false by default.

We strongly recommend performing a manual database migration before upgrading your on-premises instance to avoid extended startup times.

Pact V4 does not include a dedicated messages collection. Instead, it uses a single interactions collection, where each interaction has a type value of one of the following:

Refer to the Pact specification for details.

The migration process must inspect all existing Pact versions to correctly determine whether messages are present. This requires evaluating the Pact specification version and the interaction types contained within each Pact.

These changes ensure that existing V4 Pacts behave correctly when using can-i-deploy and that metrics and reporting related to message-based interactions are accurate.