Conversation
|
This is published as a test gem to https://rubygems.org/gems/pact-v2 there are two versions. the first contains only the v1 deps, the second contains both v1 & v2 deps. It doesn’t seem rubygems supports conditional gems ( i wanted to control it by env var ) i did look at a ruby extension to install additional gems but these wouldn’t be known to bundler the test gem will ultimately be deleted, so please don’t rely in production. ty |
PACT_RUBY_V2_ENABLE=true to opt into new code PACT_RUBY_V1_ENABLE=false to disable old code PACT_RUBY_V1 is enabled by default PACT_RUBY_V2 is disabled by default
contentType null semver values notEmpty statusCode
|
Lets go! For anyone who comes across this, if I have inadvertently broken your workflow, you may want to pin to the release prior to this going out https://github.com/pact-foundation/pact-ruby/releases/tag/v1.66.2 it has been designed to work side by side, so the only blocker for people I imagine, will be the new set of dependencies. In version 2, the old pact-ruby v1 interface will be removed, and the v2 namespaced code will be moved to the root |
We would like to implement Pact V3 & V4 Specification support for Pact Ruby enabled via the rust core
Pact Ruby V2
Fixes #317, #318, #319
Documentation
https://github.com/pact-foundation/pact-ruby/blob/feat/v2/documentation/README_V2.md
Delivered Features
Validation
The following projects were designed for pact-ruby-v1 and have been migrated to pact-ruby-v2. They can serve as an example of the work required.
V3 Related Issues
provider_state(v3) #168V4 Related Issues