do not fail if the spec defines unsupported security requirements (004729a)
BREAKING CHANGES
Prior to this change the tool used to fail when a pact request with no apparent auth was validated against a swagger operation containing security requirements both supported and unsupported by the tool (e.g. basic auth and OAuth2). Now if at least one unsupported security requirement is defined in the swagger operation the validation will pass. It is recommended that consumers and providers coordinate upgrading to this release so that both sides agree on what is considered valid vs invalid.
skip request and response body validation when the content-type is unknown (d400a1e)
Features
add configurable object depth output to CLI (ecfa0c0)
BREAKING CHANGES
Prior to this change the tool used to fail when a pact response body was validated against an unsupported swagger mime type. Now when an unsupported mime type is encountered request body validation is skipped. It is recommended that consumers and providers coordinate upgrading to this release so that both sides agree on what is considered valid vs invalid.
removed swagger warnings from validation results (9a3b757)
BREAKING CHANGES
Removed support for node 4.x. Migrate to node 6.x or higher.
Prior to this change swagger-mock-validator would return any pact/swagger warnings or errors as part of the validation result. Now when a validation error is encountered with a swagger or pact file the tool will fail with an error. Warnings are no longer reported at all. The list of validation result codes returned by the programatic API have been updated to reflect this change.