1.37.2

Release date

August 19, 2025

Features

General features

  • We removed redundant metadata from the root span emitted by OpenTelemetry instrumentation.

  • We added a delete action for requests on the /pacticipants/:pacticipant_name/versions/:pacticipant_version_number endpoint for users with appropriate permissions.

Bi-Directional Contract Testing (BDCT)

  • Now we support discriminator.mapping to improve schema compatibility in BDCT workflows.

  • We published new BDCT API endpoints:

    • /contracts/bi-directional/provider/{providerName}/version/{providerVersionNumber}/consumer/{consumerName}/version/{consumerVersionNumber}/cross-contract-verification-results

    • /contracts/bi-directional/provider/{providerName}/version/{providerVersionNumber}/consumer/{consumerName}/version/{consumerVersionNumber}/consumer-contract-verification-results

    • /contracts/bi-directional/provider/{providerName}/version/{providerVersionNumber}/consumer/{consumerName}/version/{consumerVersionNumber}/provider-contract-verification-results

    • /contracts/bi-directional/provider/{providerName}/version/{providerVersionNumber}/consumer/{consumerName}/version/{consumerVersionNumber}/provider-contract

    • /contracts/bi-directional/provider/{providerName}/version/{providerVersionNumber}/consumer/{consumerName}/version/{consumerVersionNumber}/consumer-contract

    • /contracts/bi-directional/provider/{providerName}/version/{providerVersionNumber}/cross-contract-verification-results

    • /contracts/bi-directional/provider/{providerName}/version/{providerVersionNumber}/consumer-contract-verification-results

    • /contracts/bi-directional/provider/{providerName}/version/{providerVersionNumber}/consumer-contract

    • /contracts/bi-directional/provider/{providerName}/version/{providerVersionNumber}/provider-contract-verification-results

    • /contracts/bi-directional/provider/{providerName}/version/{providerVersionNumber}/provider-contract

    See the API documentation for details on using these endpoints.

Fixes

  • We addressed security vulnerabilities by updating affected packages. See CVE advisories for more information.

Migration notes

  • You do not have to take any migration steps for this release.

In this section:
© 2025
Publication date: