Release - Pact FFI Library 0.3.15 New release published by rholshausen Bugfix + FFI functions to support plugin authors • 2f0ada6 - chore: Upgrade pact_verifier to 0.13.16 • 246c073 - chore: Upgrade pact_mock_server to 0.9.5 • 2802fff - chore: Upgrade pact_matching to 0.12.15 • c9721fd - chore: Upgrade pact_models to 1.0.1 and pact-plugin-driver to 0.1.16 • 2e5823a - feat: add custom-header to the old FFI args for implementations that have not moved to handles • 570e33c - feat: add FFI function to return generator JSON • 7a2686e - feat: add function to get matching rule as JSON • cfc565e - feat: add docs on the matching rule IDs • 18e1e11 - feat: add an iterator over the matching rules from a matching definition expression • e21d345 - feat: add FFI function to parse JSON to a Pact model • b7c010e - feat: add generator FFI functions • f7b561e - feat: add FFI function to get the generator from a matching definition • 768a132 - feat: add FFI function to parse a matching definition expression pact-foundation/pact-reference

Super stoked at the new changes to the FFI. I would imagine this kind of change should be at minor bump, not a patch, as we are introducing new features. It makes it difficult to look through a change log and say these are the new features I want, so I will update. Patch, I would expect to consume as an author without thinking and nothing should break for my end users. New features, means the author may need to do work, to bring new features to the masses. semver tag diff between patch versions https://github.com/pact-foundation/pact-reference/compare/libpact_ffi-v0.3.14...libpact_ffi-v0.3.15 For example this goldie https://github.com/pact-foundation/pact-reference/pull/229 is tucked away in a patch release https://github.com/pact-foundation/pact-reference/commit/768a132beec12daf6f1ce9e95f4b19ea86555eaa