[no ci] prep release 1.3.0

Author: ptrthomas

README.md

@@ -182,7 +182,8 @@ And you don't need to create additional Java classes for any of the payloads tha
     | <a href="#match-contains"><code>match contains</code></a>
     | <a href="#match-contains-only"><code>match contains only</code></a>
     | <a href="#match-contains-any"><code>match contains any</code></a>
-    | <a href="#match-contains-deep"><code>match contains deep</code></a>    
+    | <a href="#match-contains-deep"><code>match contains deep</code></a>
+    | <a href="#match-contains-only-deep"><code>match contains only deep</code></a>       
     | <a href="#not-contains"><code>match !contains</code></a>
     | <a href="#match-each"><code>match each</code></a>
     | <a href="#match-header"><code>match header</code></a>    
@@ -267,6 +268,7 @@ And you don't need to create additional Java classes for any of the payloads tha
 * Easily invoke JDK classes, Java libraries, or re-use custom Java code if needed, for [ultimate extensibility](#calling-java)
 * Simple plug-in system for [authentication](#http-basic-authentication-example) and HTTP [header management](#configure-headers) that will handle any complex, real-world scenario
 * [Cross-browser Web UI automation](karate-core) so that you can test *all* layers of your application with the same framework
+* Visual Validation via the built-in [image comparison](#compare-image) capabilities
 * Cross platform [Desktop Automation](karate-robot) that can be [mixed into Web Automation flows](https://twitter.com/ptrthomas/status/1215534821234995200) if needed
 * Option to invoke via a [Java API](#java-api),  which means that you can easily [mix Karate into Java projects or legacy UI-automation suites](https://stackoverflow.com/q/47795762/143475)
 * [Save significant effort](https://twitter.com/ptrthomas/status/986463717465391104) by re-using Karate test-suites as [Gatling performance tests](karate-gatling) that *deeply* assert that server responses are accurate under load
@@ -317,7 +319,7 @@ All you need is available in the [`karate-core`](https://search.maven.org/artifa
 <dependency>
     <groupId>com.intuit.karate</groupId>
     <artifactId>karate-junit5</artifactId>
-    <version>1.2.0</version>
+    <version>1.3.0</version>
     <scope>test</scope>
 </dependency>
 ```
@@ -328,7 +330,7 @@ If you want to use [JUnit 4](#junit-4), use `karate-junit4` instead of `karate-j
 Alternatively for [Gradle](https://gradle.org):
 
 ```yml
-    testCompile 'com.intuit.karate:karate-junit5:1.2.0'
+    testCompile 'com.intuit.karate:karate-junit5:1.3.0'
 ```
 
 Also refer to the wiki for using [Karate with Gradle](https://github.com/intuit/karate/wiki/Gradle).
@@ -344,7 +346,7 @@ You can replace the values of `com.mycompany` and `myproject` as per your needs.
 mvn archetype:generate \
 -DarchetypeGroupId=com.intuit.karate \
 -DarchetypeArtifactId=karate-archetype \
--DarchetypeVersion=1.2.0 \
+-DarchetypeVersion=1.3.0 \
 -DgroupId=com.mycompany \
 -DartifactId=myproject
 ```
@@ -1540,6 +1542,8 @@ Then status 202
 ## Compare Image
 Karate provides a flexible way to compare two images to determine if they are the same or similar. This is especially useful when capturing screenshots during tests and comparing against baseline images that are known to be correct.
 
+> A stand-alone example can be found here: [`examples/image-comparison`](examples/image-comparison) along with a [video explanation](https://youtu.be/wlvmNBraP60).
+
 Below is a simple example that will compare a `baseline` image to a more recent `latest` image. An image comparison UI will also be embedded into the Karate HTML report with detailed information about any differences between the two images.
 
 ```cucumber
@@ -1613,7 +1617,6 @@ function (customConfigJson, config) {
 * configure imageComparison = { hideUiOnSuccess: true }
 ```
 
-
 Image comparison engines can also be customized:
 
 ```cucumber
@@ -2936,6 +2939,14 @@ Scenario: recurse nested array
 
 > the NOT operator e.g. `!contains deep` is not yet supported, please contribute code if you can.
 
+#### `match contains only deep`
+This is exactly like [`match ==`](#match) but the order of arrays does not matter. All arrays no matter the "depth" will be checked in this way.
+
+```cucumber
+* def response = { foo: [ 'a', 'b' ] }
+* match response contains only deep { foo: [ 'b', 'a' ] }
+```
+
 ## Validate every element in a JSON array
 ### `match each`
 The `match` keyword can be made to iterate over all elements in a JSON array using the `each` modifier. Here's how it works:

examples/consumer-driven-contracts/pom.xml

@@ -19,7 +19,7 @@
         <maven.surefire.version>2.22.2</maven.surefire.version>
         <spring.boot.version>2.3.4.RELEASE</spring.boot.version>
         <junit5.version>5.7.0</junit5.version>
-        <karate.version>1.2.0</karate.version>
+        <karate.version>1.3.0</karate.version>
     </properties>    
 
     <dependencies>

examples/gatling/build.gradle

@@ -3,7 +3,7 @@ plugins {
 }
 
 ext {
-    karateVersion = '1.2.0'
+    karateVersion = '1.3.0'
 }
 
 dependencies {

examples/image-comparison/README.md

@@ -1,5 +1,5 @@
 # Karate Image Comparison
-This project is designed to demonstrate basic usage of the [Image Comparison](https://github.com/karatelabs/karate/#compare-image) feature. 
+This project is designed to demonstrate basic usage of the [Image Comparison](https://github.com/karatelabs/karate/#compare-image) feature. You can also watch a video explanation [here](https://youtu.be/wlvmNBraP60).
 
 ## Overview
 The [Image Comparison](https://github.com/karatelabs/karate/#compare-image) feature was introduced in [Karate 1.3.0](https://github.com/karatelabs/karate/wiki/1.3.0-Upgrade-Guide).

examples/image-comparison/pom.xml

@@ -11,7 +11,7 @@
         <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
         <java.version>1.8</java.version>
         <maven.compiler.version>3.8.1</maven.compiler.version>
-        <karate.version>1.3.0-SNAPSHOT</karate.version>
+        <karate.version>1.3.0</karate.version>
     </properties>    
 
     <dependencies>

examples/jobserver/build.gradle

@@ -3,7 +3,7 @@ plugins {
 }
 
 ext {
-    karateVersion = '1.2.0'
+    karateVersion = '1.3.0'
 }
 
 dependencies {

examples/jobserver/pom.xml

@@ -11,7 +11,7 @@
         <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
         <java.version>1.8</java.version>
         <maven.compiler.version>3.8.1</maven.compiler.version>
-        <karate.version>1.2.0</karate.version>
+        <karate.version>1.3.0</karate.version>
     </properties>    
 
     <dependencies>           

examples/mobile-test/pom.xml

@@ -12,7 +12,7 @@
         <java.version>1.8</java.version>
         <maven.compiler.version>3.8.1</maven.compiler.version>
         <maven.surefire.version>2.22.2</maven.surefire.version>
-        <karate.version>1.2.0</karate.version>
+        <karate.version>1.3.0</karate.version>
     </properties>
 
     <dependencies>

examples/mock-servlet/pom.xml

@@ -12,7 +12,7 @@
         <java.version>1.8</java.version>
         <maven.compiler.version>3.6.0</maven.compiler.version>
         <spring.boot.version>2.5.12</spring.boot.version>
-        <karate.version>1.2.0</karate.version>
+        <karate.version>1.3.0</karate.version>
     </properties>    
 
     <dependencies>

examples/profiling-test/pom.xml

@@ -11,7 +11,7 @@
         <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
         <java.version>1.8</java.version>
         <maven.compiler.version>3.6.0</maven.compiler.version>
-        <karate.version>1.2.0</karate.version>
+        <karate.version>1.3.0</karate.version>
         <gatling.plugin.version>4.1.1</gatling.plugin.version>
     </properties>