From 9bd4cc01a6bc60f9c98961e12958eb03bc106c3f Mon Sep 17 00:00:00 2001
From: maximilianpilz <104556470+maximilianpilz@users.noreply.github.com>
Date: Thu, 22 Feb 2024 18:21:20 +0100
Subject: [PATCH] bump t2iapi version to 4.1.0

---
 CHANGELOG.md  | 4 ++++
 README.md     | 2 +-
 sdccc/pom.xml | 2 +-
 3 files changed, 6 insertions(+), 2 deletions(-)

diff --git a/CHANGELOG.md b/CHANGELOG.md
index 90657606..0988b5f7 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -10,6 +10,10 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 - a command line parameter to change the log level threshold of the log file
 
+### Changed
+
+- t2iapi version to 4.1.0
+
 ### Fixed
 
 - a performance issue with xml unmarshalling due to finding an interface implementation for TransformerFactory
diff --git a/README.md b/README.md
index c709fd12..14ab4ad0 100644
--- a/README.md
+++ b/README.md
@@ -130,7 +130,7 @@ Enable=true
 will make all devices match during discovery.
 
 ### Manipulation API
-The test tool uses *T2IAPI* version `3.0.0`. The *T2IAPI* is required for some test cases to put the DUT in a certain
+The test tool uses *T2IAPI* version `4.1.0`. The *T2IAPI* is required for some test cases to put the DUT in a certain
 state, or to trigger a certain behavior. When using SDCcc with automated manipulations, it must be ensured that the same
 version of *T2IAPI* is used for the test execution by both parties. It must also be ensured that the device's 
 manipulations are implemented according to the descriptions in the T2IAPI sources. Further information can be found 
diff --git a/sdccc/pom.xml b/sdccc/pom.xml
index 1a1d9a93..210f1fa8 100644
--- a/sdccc/pom.xml
+++ b/sdccc/pom.xml
@@ -172,7 +172,7 @@
         <dependency>
             <groupId>com.draeger.medical</groupId>
             <artifactId>t2iapi</artifactId>
-            <version>3.0.0</version>
+            <version>4.1.0</version>
         </dependency>
 
         <dependency>