From 2f4b043384284f9dad59938f139ce2e581a96d35 Mon Sep 17 00:00:00 2001
From: berkaycanbc <berkay.can@camunda.com>
Date: Tue, 6 Aug 2024 14:48:57 +0300
Subject: [PATCH] fix(build): pin camunda-dmn-model to a specific version

We get dependency convergence error while releasing 8.2.30. That is,
camunda-dmn-model depends on camunda-xml-model:jar:7.18.0 while zeebe-bpmn-model
depends on 7.22.0-alpha3. To fix the issue, we can pin the version to the upgraded one.
---
 pom.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/pom.xml b/pom.xml
index d2a3bcb2..65cc3052 100644
--- a/pom.xml
+++ b/pom.xml
@@ -50,7 +50,7 @@
     <dependency.assertj.version>3.24.2</dependency.assertj.version>
     <dependency.awaitility.version>4.2.0</dependency.awaitility.version>
     <dependency.bytebuddy.version>1.14.3</dependency.bytebuddy.version>
-    <dependency.camundamodel.version>7.18.0</dependency.camundamodel.version>
+    <dependency.camundamodel.version>7.22.0-alpha3</dependency.camundamodel.version>
     <dependency.classgraph.version>4.8.157</dependency.classgraph.version>
     <dependency.commons.version>3.12.0</dependency.commons.version>
     <dependency.errorprone.version>2.18.0</dependency.errorprone.version>