Release - v2.0.9 New release published by YOU54F What's Changed • build(deps): bump google.golang.org/protobuf from 1.34.2 to 1.35.1 by @dependabot in #459 • build(deps): bump google.golang.org/grpc from 1.66.0 to 1.67.1 by @dependabot in #460 • fix: ensure sync messages write metadata to both req & res by @YOU54F in #461 • build(deps): bump google.golang.org/protobuf from 1.35.1 to 1.35.2 by @dependabot in #463 • chore(ci): upgrade macos-12 to macos-13 by @JP-Ellis in #468 • docs: pact-go supported platforms by @YOU54F in #466 • chore(ci): prevent duplicate ci triggers by @JP-Ellis in #476 • chore: Configure Renovate by @renovate in #467 • fix(deps): update module github.com/spf13/afero to v1.12.0 by @renovate in #483 • fix(deps): update module github.com/linkedin/goavro/v2 to v2.13.1 by @renovate in #482 • fix(deps): update module google.golang.org/protobuf to v1.36.3 by @renovate in #486 • fix(deps): update module github.com/stretchr/testify to v1.10.0 by @renovate in #487 • Improving Provider VerifyRequest - ProviderBaseURL documentation. by @marcusvnac in #464 • fix(deps): update module gopkg.in/yaml.v2 to v3 by @renovate in #489 • Deps/go mod tidy by @YOU54F in #492 New Contributors • @JP-Ellis made their first contribution in #468 • @renovate made their first contribution in #467 • @marcusvnac made their first contribution in #464 Full Changelog: v2.0.8...v2.0.9 pact-foundation/pact-go

Release - v2.0.10 New release published by YOU54F What's Changed • fix: update pact-ffi to v0.4.26 by @YOU54F in #493 Full Changelog: v2.0.9...v2.0.10 pact-foundation/pact-go

Release - v2.0.10 New release published by YOU54F What's Changed • fix: update pact-ffi to v0.4.26 by @YOU54F in #493 Full Changelog: v2.0.9...v2.0.10 pact-foundation/pact-go

Release - v2.1.0 New release published by YOU54F What's Changed • fix(deps): update module google.golang.org/grpc to v1.69.4 by @renovate in #488 Breaking Change • chore(deps)!: require minimum go version 1.22 by @YOU54F in #490 Full Changelog: v2.0.10...v2.1.0 pact-foundation/pact-go

hey team!, we are trying to write contracts tests using pact-go and we are getting this failure in our pipeline

/usr/bin/ld: cannot find -lpact_ffi: No such file or directory
collect2: error: ld returned 1 exit status

can you please help to fix this ?

@Tom Lopez has left the channel

Release - v2.2.0 New release published by YOU54F What's Changed • feat: support linux musl by @YOU54F in #454 Full Changelog: v2.1.0...v2.2.0 pact-foundation/pact-go

Hey Team, I have an another question. I am writing contract testing following this example contract test file :- https://github.com/pact-foundation/pact-go/blob/master/examples/basic_test.go But when I am adding one another test case in the same code, Interactions are not getting merged in same pact file. I guess interactions should be merged as it is an array of interactions in pact output.

Do they have unique interaction descriptions?

Yes

Set logs to debug and have a see if anything jumps out about writing interactions

Feel free to share code examples also

Hello, I already posted my question in #C9VPNUJR2, but I feel it may be related to pact-go, we get a strange error when using certain selector:

pact_verifier: Failed to load pact - Failed to load pact from '<https://pact-broker.spatium-iot.com>': Error with the content of a HAL resource - Expected either a "*" or path identifier in path expression "$.query.$" at index 8

when we use one of those selector: • DeployedOrReleased • Environment • Deployed We tried a lot of possibilities, but only “Latest: true” works. since we have multiple environments, we also want DeployedOrReleased, which was working until recently

@Romain Létendart has left the channel

Hello together, i am doing some Pact Messaging Tests and just saw in the pactBroker that it says the pacts are verified by pact-rust. Is this normal or a overlook of the implementation?

{
  "providerName": "MQTTProducer",
  "providerApplicationVersion": "1.0.0",
  "success": true,
  "verificationDate": "2025-02-03T05:54:37+00:00",
  "testResults": [
    {
      "interactionId": "4502629169ea07b9fd7c9fd70c772553a1b4407d",
      "success": true
    }
  ],
  "verifiedBy": {
    "implementation": "Pact-Rust",
    "version": "1.2.5"
  },
  "_links": {
    "self": {
      "title": "Verification result",
      "name": "Verification result 201 for Pact between MQTTConsumer (1.0.1) and MQTTProducer",
      "href": "<http://localhost:9292/pacts/provider/MQTTProducer/consumer/MQTTConsumer/pact-version/cd421621766dde56e9e01a0c8a8b47c4b5f63b40/verification-results/201>"
    },
    "pb:pact-version": {
      "title": "Pact",
      "name": "Pact between MQTTConsumer (1.0.1) and MQTTProducer",
      "href": "<http://localhost:9292/pacts/provider/MQTTProducer/consumer/MQTTConsumer/pact-version/cd421621766dde56e9e01a0c8a8b47c4b5f63b40/metadata/Y3ZuPTEuMC4x>"
    },
    "pb:triggered-webhooks": {
      "title": "Webhooks triggered by the publication of this verification result",
      "href": "<http://localhost:9292/pacts/provider/MQTTProducer/consumer/MQTTConsumer/pact-version/cd421621766dde56e9e01a0c8a8b47c4b5f63b40/verification-results/201/triggered-webhooks>"
    }
  }
}

When trying to run provider pact tests, getting this error:

Undefined symbols for architecture arm64:
  "_pactffi_with_metadata", referenced from:
      __cgo_b3f3fec7e6e1_Cfunc_pactffi_with_metadata in 000003.o
ld: symbol(s) not found for architecture arm64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

Anyone ever see this before?

@Spencer has left the channel

Release - v2.3.0 New release published by mefellows ## Changelog • bd5ea1c chore(release): release v2.3.0 • e6e2c11 feat: add metadata.pact-go.version to pact file • 1e4ecc7 fix(deps): update module github.com/spf13/cobra to v1.9.1 (#502) • e05acfd fix(deps): update module google.golang.org/grpc to v1.70.0 (#495) • 6c40e0b fix(deps): update module google.golang.org/protobuf to v1.36.5 (#496) • 8d700cc fix: strip v prefix from pact-go verifier version pact-foundation/pact-go

Is there a pact-mock-server that supports the latest version of PACT?

Im currently using https://github.com/pact-foundation/pact-mock_service for a consumer test which I can write out a PACT contract, but we I verify the contract I am getting an error stating that 'type' attribute is missing, so I suspect the pact-mock-service is runnign an older version of PACT

@Martin Mineo has left the channel

Release - v2.4.0 New release published by mefellows ## Changelog • 9e92fc2 chore(deps)!: require minimum go version 1.23 • 6ba0381 chore(release): release v2.4.0 • ada7782 fix(deps): update module google.golang.org/grpc to v1.71.0 pact-foundation/pact-go

Release - v2.4.1 New release published by mefellows ## Changelog • 9e92fc2 chore(deps)!: require minimum go version 1.23 • 2f21a81 chore(release): release v2.4.0 • 0f6597b chore(release): release v2.4.1 • ada7782 fix(deps): update module google.golang.org/grpc to v1.71.0 • eba6b2c fix: update pact-ffi to 0.4.27 (#509) pact-foundation/pact-go

Hi Guys, Is anyone facing issues with Pact-Go compatibility on Go 1.22? Running:

go install <http://github.com/pact-foundation/pact-go/v2@latest|github.com/pact-foundation/pact-go/v2@latest>

fails, but if I remove

@latest

, it works fine. Would it be possible to document Go version compatibility in the README? That would be really helpful. Thanks

@Erich Zimmerman has left the channel

hello lovely people. I am having a problem with pact-go Provider verification test where it cannot read the provider states from a contract json generated by pact-jvm. There is a mismatch in how the contract JSON is generated by pact-jvm and pact-go. Let me explain a bit more. We have a Consumer test written in Java with pact-jvm, snippet below:

@Pact(provider = PROVIDER, consumer = CONSUMER)
    public RequestResponsePact operationalHealth(PactDslWithProvider builder) {
        return builder
            .given("IFE functionalHealth is Operational")
            .uponReceiving("A request for IFE availability status Operational")
...
...
...

this will generate a contract where provider state is defined as an Array of Strings:

"interactions": [
    {
      "description": "A request for IFE availability status Operational",
      "providerStates": [
        {
          "name": "IFE functionalHealth is Operational"
        }
      ],

on the provider side we have a Provider test written in Golang with pact-go, snippet as follows:

StateHandlers: models.StateHandlers{
			"IFE functionalHealth is Operational": func(setup bool, ps models.ProviderState) (models.ProviderStateResponse, error) {
...
...
...

and the problem is when I run this test it doesn't seem to read the provider states at all because when I tried to pusposely break it it was still passing. I went ahead and created a similar consumer test in Golang, like this:

mockProvider.
		AddInteraction().
		Given("IFE functionalHealth is Operational").
		UponReceiving("A request for IFE availability status Operational").
...
...
...
...

after running this test I got the contract JSON where provider state is defined as String:

"interactions": [
    {
      "description": "A request for IFE availability status Operational",
      "providerState": "IFE functionalHealth is Operational",

this contract is then consumed and parsed correctly by provider test because when I try to break it I see a corresponding provider state failing. Are you guys aware of similar issues? If so how do I go about addressing it? Thank you in advance.

Hello, Is there an equivalent setting in Go for the Java attribute

IgnoreNoPactsToVerify

?

We recently started incorporating contract testing in our tests using pact-go. This all felt very easy and natural, but things got a bit awkward for integration tests. Multiple services need to be mocked, so I'm nesting the

ExecuteTest

methods of the different MockProviders a bit like so

mockProvider1.ExecuteTest(t, func(service1Config consumer.MockServerConfig) {
	err := mockProvider2.ExecuteTest(t, func(service2Config consumer.MockServerConfig) {
		c, err := createClient(service1Config, service2Config)
		// test logic here
	})
})

Is this the way to do it or am I doing something wrong? Should I not use contract testing in the integration tests, or am I missing a pattern in the pact-go lib?

@Dominick Campbell has left the channel

Hey everyone, my team is looking start adding consumer driven contract tests as part of the tools we use with testing our microservices and one of the things that we want to do as a start is refactor the way setup our services. By this I mean currently in the

main.go

file for a service, there is a lot of setup (e.g grpc server, db connections, config refs) and we would like to abstract this to a service file so that it's no longer done in

main.go

. Is this the right approach or are there better established patterns to use?