Is this a good opportunity to re-think automating the release process from GitHub?

Probably, but I couldn't be bothered doing it

I don't gamble, so you don't have to worry about me winning any lotteries

Do you travel on public transport?

Just clarifying - what time is our maintainer meet tonight? I think 8pm AEST / 12pm CET / 6am ET?

In 1 hour from now?

haha thanks all 👋

What's on the agenda for tonight? I'm still behind on my actions and need to get some other urgent stuff done if nothing pressing

FYI I think Yousaf and Jo are at a conference. I could use the time tonight to work on my commitments (retro follow up and progressing the JS PR)vif we don't have much to discuss? I'm also likely to be slightly late (kids)

i’ll be about. we don’t head off till later this eve. all good if you want to get your head down buddy

Ah cool. I'll aim to be there. Initiating bed time routine in 3-2-1...

I would like a new version for pact-protobuf-plugin and pact-ffi, can you release them for me @rholshausen?

Hey all, Welcome @Kevin Vaz who recently joined the PactFlow team and will be helping triage and work on some issues in the Pact-Python space. alongside @Joshua Ellis who has been doing awesome work. I’ve created a pact-python-triagers team and added kevin into it, rather than full maintainer/admin rights. Josh feel free to amend to suit.

Sorry folks, I need to skip on tonight’s meeting. I need to get something done tonight (insert MS Powerpoint emoji!)

blobwave On Friday, some CLI tooling changes were merged to to help the migration/adoption of our rust based tooling, over our ruby tooling. All rust cli tooling is now available in a consolidated docker image and standalone package, these are additions to the existing ruby consolidated cli packages. To support this 1. pact-ruby-cli has been renamed to pact-docker-cli 2. pact-ruby-standalone has been renamed to pact-standalone Ruby packages have been marked as legacy in cli docs, with exception of the pact_broker-client. • https://github.com/pact-foundation/pact-docker-cli/pull/135 • https://github.com/pact-foundation/pact-standalone/pull/146 Updated docs / repo links • https://docs.pact.io/implementation_guides/overview

Hey folks, I’ll be there tonight (albeit will need to drop a little earlier to get to another call). Looking forward to seeing you 👋

I’ve dropped these crate owners (pact) a message to see if we can claim it as they have renamed to codas and have a notice in place about transferring https://crates.io/crates/pact

this is also unfortunate 😅 i might drop them a message whilst I am at it https://crates.io/crates/pact-cli

Sorry folks, I realised the maintainer invite dropped out of my calendar. I wouldn’t have made last week anyway as I was on leave. I should be right for next Wednesday

someone trying to add pact_broker-client as pact-cli to homebrew-core https://github.com/pact-foundation/pact_broker-client/pull/195 kind of nice to have it in homebrew-core, but without having a live url to update, it makes it more awkward to use to update (an extra hope out of our control), plus those type of package managers don’t usually like have meta cli packages that bundle up many clis ( I got grief from scoop about it when looking to create listed packages for there)

I asked some questions to see if we be viable to be the core,, but to also address some concerns about the meta cli

came across this at the weekend https://github.com/kmdreko/venator you can stream rust tracing logs to it, which is quite nice. (and view otel traces/spans) although it needs some UI love on macos as navigation isn't quite right Also finally got round to having a play with https://rybbit.local/ at tracking calls from the rewritten pact-broker-cli. Went on a bit of a diversion and added it into a local copy of pact-reference and was able to get a nice view of the calls. I reused and extended the existing metrics to allow configuration to GA, or a locall rybbit instance but could be extended for other providers Then took a bit of wander into otel, adding it into the pact_broker, ruby pact_broker-client and rust pact-broker-cli. Have the traces nicely connected into a span between ruby -> ruby but not rust -> ruby yet Once I've got that connected, I'd love to get otel hooked up with verifier and/or mock server to see what it could look like

Curl as debug, I tried this out and modified the code a bit. https://gitlab.com/mcarton/dbg_as_curl Francis showed something similar she did over in JVM https://github.com/pact-foundation/pact-jvm/issues/1507 I think this would be gamechanger for me for http debugging (if you discount the fact that your provider wont have a state server setup if you run it locally to send the curl request against. )

renovate will be renamed to mend, so if you have any filters which exclude bots, you will need to rename to add mend (I believe) from reading this https://github.com/renovatebot/renovate/discussions/37842 shouldn’t make much difference to day to day ( i have a saved click house query for pact-foundation and a few other orgs but exclude bots for my sanity)

bye. bye macos x86_64 https://github.blog/changelog/2025-09-19-github-actions-macos-13-runner-image-is-closing-down/ we will probably need to switch to using rosetta, for x64 compilation, as

macos-15-intel

I believe is a chargable runner, and x64 will be dropped by macos anyway, but supporting older x86_64 clients should still be on our radar, as it generally is just setting an xcode env var. If/when rosetta gets removed, it’ll be a different story, but as it is used for x64 emulation of linux, which has been gaining in popularity on macos, especially with apple releasing

container

(their docker alternative), I imagine it will be here for a while

pact broker client rewrite is transferred over to the pact-foundation now https://github.com/pact-foundation/pact-broker-cli released to crates/dockerhub/ghcr and available as a github action and has install scripts for windows and unix systems rockon rust

@Marko (IttyBittyApps / pact-swift) is asking if we should move https://github.com/surpher/PactSwift into the pact foundation org. I think it makes sense, given it’s replaced the previous defacto project

Any objections?

There's lots of moving parts though. I've tried to document them and set up scripts to automate most of things: •

surpher/PactSwift

is the main interface that's aiming to remove pact business logic but only act as a Swift interface •

surpher/PactSwiftMockServer

is the wrapper around

lib_pactffi

(and should delegate most/all the business logic to lib.a`. This is the working repo that does the implementation •

surpher/PactSwiftServer

is vending XCFramework binary avoiding maaaasssive repo. This is the "shareable" repo that vends the compiled results of

PactSwiftMockServer

•

surpher/PactMockServer

delivers module.modulemap to bridge Rust -> Swift

ok, seems like you're keen to take it under your wing. I'll have a think how we can approach this so you don't inherit all the crap I had to add into the history. I'll pull out a crystal bowl or ouija board to help me remember where I left it off and what would need to be done for

pact-foundation/PactSwift

and co carry on from point where it supports Swift Concurrency (eg. PactSwift

v2

).

Scratched out a few thoughts here on how we may go about supporting optionals. Feedback welcome 😉 https://github.com/pact-foundation/roadmap/discussions/128