Adam Rodger

The CI additionally would need updating to test the new target

Yep that was the same problem I had when I originally raised a PR for this and had to abandon it @YOU54F. There doesn't seem to be a reliable way...

It may be more pragmatic on Alpine to install something like https://github.com/Stantheman/gcompat to provide glibc compatibility so that the existing shared library will work, although I've not tested that.

PactNet used to have architecture specific packages but a key design goal of the major changes in 4.x was to move away from this approach. In practice it's very awkward...

Yeah I think a good next step is to start sketching out an API for the consumer and verifier sides. Presumably these are only available on the V4 spec anyway...

So the error is that the actual header doesn't match the expected one (it has a different date). Since you've used a Matcher instead of a literal value then you'd...

PactNer serialises the Matcher properly and submits it to pactffi, so it looks like this is a bug in pactffi to me https://github.com/pact-foundation/pact-net/blob/a16fac3588972006c0b1f35f934756229a3d3827/src/PactNet/RequestBuilder.cs#L352

I wonder if this is caused by https://github.com/pact-foundation/pact-reference/issues/214 The regex library on pactffi is known to be a bit quirky with inputs with partial overlaps, which all ISO dates are...

Yeah we've upgraded FFI since then so there's definitely a chance it was fixed. If you do any more testing and decide this works now then feel free to close....

PactNet 4.x+ (which is the only supported version) works in merge mode only, thus running tests will always add to an existing file instead of overwriting it. This wasn't the...