chore(docs): update versions to Operaton 2.2.1

docs/documentation/user-guide/logging.md

@@ -51,7 +51,7 @@ Add the logback dependency
 <dependency>
   <groupId>ch.qos.logback</groupId>
   <artifactId>logback-classic</artifactId>
-  <version>1.6.5</version>
+  <version>1.6.6</version>
 </dependency>
 ```
 

docs/documentation/user-guide/quarkus-integration/version-compatibility.md

@@ -95,6 +95,10 @@ Only these default combinations are recommended (and supported) by Operaton.
     <td>2.2.0</td>
     <td>3.40.1.1 (LTS)</td>
   </tr>
+  <tr>
+    <td>2.2.1</td>
+    <td>3.40.1.1 (LTS)</td>
+  </tr>
 </table>
 
 In case a certain Quarkus version has a bug, you can override the existing Quarkus version by adding the following

docs/documentation/user-guide/spring-boot-integration/version-compatibility.md

@@ -94,4 +94,8 @@ Operaton and its compatible Spring Boot Starter always share the same version. E
     <td>2.2.0</td>
     <td>4.1.2</td>
   </tr>
+  <tr>
+    <td>2.2.1</td>
+    <td>4.1.2</td>
+  </tr>
 </table>

docs/documentation/user-guide/testing/index.md

@@ -243,7 +243,7 @@ You can now see the engine database and use it to understand how and why your un
 
 ## Operaton Assertions
 
-Additional to normal JUnit assertions, [Operaton Assert](https://github.com/operaton/operaton/tree/v2.2.0/test-utils/assert) adds a fluent API for asserting typical scenarios in a process integrating with [AssertJ](https://joel-costigliola.github.io/assertj/).
+Additional to normal JUnit assertions, [Operaton Assert](https://github.com/operaton/operaton/tree/v2.2.1/test-utils/assert) adds a fluent API for asserting typical scenarios in a process integrating with [AssertJ](https://joel-costigliola.github.io/assertj/).
 
 ```java
 assertThat(processInstance).isWaitingAt("UserTask_InformCustomer");

docs/get-started/apache-maven.md

@@ -39,7 +39,7 @@ Snapshot artifacts are published to Central's snapshot repository. Add it only w
     <dependency>
       <groupId>org.operaton.bpm</groupId>
       <artifactId>operaton-bom</artifactId>
-      <version>2.2.0</version>
+      <version>2.2.1</version>
       <scope>import</scope>
       <type>pom</type>
     </dependency>
@@ -98,7 +98,7 @@ This BOM allows to use the DMN engine standalone without the BPMN engine and the
   <dependency>
     <groupId>org.operaton.bpm.dmn</groupId>
     <artifactId>operaton-engine-dmn-bom</artifactId>
-    <version>2.2.0</version>
+    <version>2.2.1</version>
     <type>pom</type>
     <scope>import</scope>
   </dependency>

docs/get-started/dmn/project-setup.md

@@ -45,7 +45,7 @@ The next step consists of setting up the Maven dependencies for your new process
   <packaging>war</packaging>
 
   <properties>
-    <operaton.version>2.2.0</operaton.version>
+    <operaton.version>2.2.1</operaton.version>
     <maven.compiler.release>11</maven.compiler.release>
   </properties>
 

docs/get-started/quick-start/service-task.md

@@ -117,7 +117,7 @@ Your pom.xml file of your project should look like this:
 	<version>0.0.1-SNAPSHOT</version>
 
 	<properties>
-		<operaton.external-task-client.version>2.2.0</operaton.external-task-client.version>
+		<operaton.external-task-client.version>2.2.1</operaton.external-task-client.version>
 		<maven.compiler.source>11</maven.compiler.source>
 		<maven.compiler.target>11</maven.compiler.target>
 	</properties>

docs/get-started/spring-boot/project-setup.md

@@ -61,7 +61,7 @@ We also use `spring-boot-maven-plugin`, which packages the Spring Boot applicati
     <java.version>17</java.version>
     <maven.compiler.release>17</maven.compiler.release>
     <spring-boot.version>4.1.2</spring-boot.version>
-    <operaton.version>2.2.0</operaton.version>
+    <operaton.version>2.2.1</operaton.version>
   </properties>
 
   <dependencyManagement>