14.4.0 (2024-10-08)
- add option to publish verification result to pact broker (3c4871d)
- add support for formatted verification results (acbfc75)
- Bearer token based auth for PactFlow Broker (f42f3ed)
- support provider branch/tags on verification published (d644079)
14.3.0 (2024-10-04)
14.2.0 (2023-10-09)
14.1.0 (2023-08-21)
14.0.0 (2023-08-04)
- explicity set additionalProperties to false (82f2a3b)
13.3.0 (2023-07-28)
13.2.0 (2023-07-04)
13.1.0 (2023-06-30)
13.0.0 (2023-06-28)
- upgrade Ajv from v6 to v8 (5a17818)
12.3.0 (2023-06-13)
- handle validations for negative scenarios (39f99b8)
12.2.0 (2023-06-05)
12.1.0 (2023-05-24)
12.0.0 (2023-05-22)
11.5.0 (2023-05-12)
- handle more varieties of json (e59bcdf)
11.4.0 (2023-05-05)
- hide debug behind feature toggle (c692494)
- log where validation passes when it should've failed (5691531)
- Respect request and response content-types (5c86507)
11.3.1 (2023-03-20)
- replace unmaintained dependency request for axios (merge from upstream) (af43f68)
11.3.0 (2022-07-07)
- add pact v4 e2e test (c6b6418)
- filter requests by type to support v4 (923f241)
- update pact parser to filter out all unsupported interaction types (343647d)
- Update pact-parser.ts (a200bf0)
11.2.0 (2022-06-14)
11.1.0 (2022-06-14)
- Convert pact spec 3 headers to v1 format (a0584b0)
11.0.0 (2022-04-22)
- Will change default behaviour to no longer allow additional properties in response by default. Will go out as a major release
10.3.0 (2022-04-22)
- support for open string-valued properties (178240e)
10.2.1 (2022-04-20)
10.2.0 (2022-04-20)
10.1.4 (2022-04-20)
- support for open string-valued properties (178240e)
10.1.3 (2022-03-15)
- do not warn if mock expects content-type in HEAD response and no mime type are defined in the spec (b6aabbc), closes #75
10.1.2 (2022-01-10)
10.1.1 (2021-06-08)
10.1.0 (2021-02-23)
- support Pact v3 query format (5bf15c3)
10.0.1 (2021-02-17)
- accept header should match mime-types of any operation responses for openapi 3 (4f0eb55), closes #87
10.0.0 (2020-11-03)
- fix bug when both nullable and swagger custom formats are defined (ed4acf9)
- bump dependencies (9b959be)
- Dropped support for NodeJS v6 and v8. Migrate to NodeJS v10 or above.
9.0.0 (2019-11-07)
- correctly validate request bodies containing a JSON null or false value (79fae8c)
- support the nullable attribute for data types (d3c13cc)
- Prior to this change the tool used to succeed when a pact request specified a request body containing solely the JSON literals ‘null' or 'false’, regardless of what the spec accepted. Now, request bodies with such values will only pass validation if the spec is okay with them.
8.0.0 (2019-09-18)
- do not fail if an OpenApi 3 spec defines an empty security requirement (f42ceb1)
- Prior to this change the tool used to fail when a pact request with no auth was validated against an OpenApi 3 operation containing a security requirement (e.g. basic auth) plus an empty security requirement (which is normally used to represent that auth is optional). Now empty security requirements are considered for OpenApi3 specs hence not failing when the request lacks auth attributes.
7.0.0 (2019-08-26)
- do not fail if the spec defines unsupported security requirements (004729a)
- 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.
6.0.2 (2019-06-14)
6.0.1 (2019-02-27)
- definitions no needed for parameter schema validation (4a693d6)
6.0.0 (2019-02-05)
- skip request and response body validation when the content-type is unknown (d400a1e)
- add configurable object depth output to CLI (ecfa0c0)
- 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.
5.2.1 (2018-10-02)
- validate wildcards for media types, drop buggy support for media type parameters (602abbd)
5.2.0 (2018-09-13)
5.1.0 (2018-09-06)
5.0.1 (2018-08-29)
- pin swagger-parser to avoid breaking changes when validation logic is changed (ab6c04c)
5.0.0 (2018-08-23)
- do not crash if path-item contains an ^x- property (d57f887)
- fixed issue with format not being validated for bodies containing primitive values (dca4654)
- use case-sensitive matching for query string parameters (f269cd9)
- removed support for node version 4.x and added build test for node version 10.x (52c4963)
- add support for OpenApi 3 specs (19deb93)
- removed swagger warnings from validation results (9a3b757)
- 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.
4.0.1 (2018-07-05)
4.0.0 (2018-04-13)
- format validators for int32, int64, float and double no longer accept spaces and now test for the full range of accepted values (a38b085), closes #67
- Prior to this change the tool used to accept blank spaces in path parameters for int32, int64, float and double formatted numbers. A bug has been fixed to disallow blank spaces. This means some mock responses that were previously considered valid will now be considered invalid. This change has also updated the int64 and double format validators to now test for the full range of values these types support. This means some mock responses that were previously considered invalid will now be considered valid.
It is recommended that consumers and providers coordinate upgrading to this release so that both sides agree on what is considered valid vs invalid.
3.0.0 (2018-01-31)
- content negotiation between request content type header and consumes values in spec (100aaf3)
- This release contains a bug fix for the way content type headers were being validated. As a result of this bug fix some mocks and specs which were previously considered valid will now be considered invalid.
2.2.3 (2017-12-21)
- bump swagger-tools to resolve issue where the tool locks up when swagger examples contain a length property (46dac30)
2.2.2 (2017-11-29)
- reverting fix for content negotiation, this will be re-released as a major version (c72993f)
2.2.1 (2017-11-29)
- fix content negotiation between request content type header and consumes values in spec (4953743)
2.2.0 (2017-09-01)
- add javascript api (ea0f098)
2.1.0 (2017-08-07)
2.0.2 (2017-07-14)
- spec warnings were not shown if mock validation returns errors (c1328a8)
2.0.0 (2017-07-11)
- add support for circular references in the swagger file (dd61f7b), closes #60
- only output mockDetails and specDetails when they relevant (8486bf8), closes #56
- Prior to this change the tool used to disallow additional properties in response mocks unless the schema explicitly allowed additional properties. To support the allOf keyword correctly this behavior has been changed. Now additional properties are allowed in response mocks unless a schema explicitly disallows them. This means some mock responses that were previously considered invalid will now be considered valid. It is recommended that consumers and providers coordinate upgrading to this release so that both sides agree on what is considered valid vs invalid.
- swagger-mock-validator now supports validating schemas containing circular references. Prior to this change schemas containing circular references were ignored. If you have a schema that contains circular references and a mock that is not compatible with that schema the swagger-mock-validator will now fail. It is recommended that consumers and providers coordinate upgrading to this release so that both sides agree on what is considered valid vs invalid.
1.0.0 (2017-03-24)
- the order of security requirements impacts validation results (07a7122)
- add opt-in analytics (6439444), closes #54
- rename project to swagger-mock-validator (2594491), closes #16
- The name of the module has changed from “@atlassian/swagger-pact-validator” to “swagger-mock-validator”. To migrate you need to rename the dependency in your package.json and update any code that invokes this cli took from “swagger-pact-validator” to “swagger-mock-validator”.
0.0.31 (2017-02-22)
0.0.30 (2017-02-20)
0.0.28 (2017-02-16)
0.0.27 (2017-02-08)
0.0.26 (2017-01-24)
0.0.25 (2017-01-23)
- add validation for swagger consumes (660c618), closes #34
- add validation for swagger produces (2a341ab), closes #33
0.0.24 (2017-01-17)
- correctly extract provider state from pact interactions (d4dd4fe)
0.0.23 (2017-01-16)
0.0.22 (2017-01-12)
0.0.21 (2017-01-06)
0.0.20 (2017-01-04)
0.0.19 (2017-01-03)
0.0.18 (2016-12-30)
- add validation for enum (e83600e), closes #40
- add validation for maximum and exclusiveMaximum (8371cc2), closes #41
- add validation for maxLength and minLength (8aa82e8), closes #45 #46
- add validation for minimum and exclusiveMinimum (11e7eba), closes #43
- add validation for multipleOf (bfe149e), closes #48
- add validation for pattern (d20251e), closes #47
0.0.17 (2016-12-29)
0.0.16 (2016-12-19)
- add counts of errors and warnings detected (0846030), closes #38
- add validation for response headers (2218cb3), closes #5
0.0.15 (2016-12-14)
- display warnings when validation succeeds (1be61b5)
0.0.14 (2016-12-14)
- add validation for request headers (2676b27), closes #2 #7
- undefined non-standard request headers are now warnings (adca8bd)
0.0.13 (2016-12-07)
0.0.12 (2016-12-05)
- add validation for response body (ac2c479), closes #6
- reduce verbosity of the output when errors are detected (d300546), closes #27
0.0.11 (2016-11-30)
- improve validation speed for large swagger files (e009399)
0.0.10 (2016-11-24)
0.0.9 (2016-11-21)
- partial path matching causing exceptions (8507ff5)
0.0.8 (2016-11-18)
0.0.7 (2016-11-17)
- handle undefined path parameters when method is missing (b595073)
0.0.6 (2016-11-17)
0.0.5 (2016-11-08)
0.0.4 (2016-09-13)
- add support for retrieving pact and swagger files via urls (ab248dc)
0.0.3 (2016-09-01)
- path parameter parser no longer case sensitive for request method (cab9c81)