This is an automated email from the ASF dual-hosted git repository.

yamer pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/incubator-kie-tools.git


The following commit(s) were added to refs/heads/main by this push:
     new 7284f7dfc97 NO-ISSUE: Process security example not working after 
Quarkus Upgrade (#3488)
7284f7dfc97 is described below

commit 7284f7dfc979049275ae7b4c1423b9e119c87039
Author: Nithin R Krishnan <[email protected]>
AuthorDate: Fri Mar 6 15:50:47 2026 +0530

    NO-ISSUE: Process security example not working after Quarkus Upgrade (#3488)
    
    Co-authored-by: Nithin R Krishnan <[email protected]>
---
 examples/process-security/kie-service-1/pom.xml | 2 +-
 examples/process-security/kie-service-2/pom.xml | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/examples/process-security/kie-service-1/pom.xml 
b/examples/process-security/kie-service-1/pom.xml
index 9531ad86ff1..b0291a6570f 100644
--- a/examples/process-security/kie-service-1/pom.xml
+++ b/examples/process-security/kie-service-1/pom.xml
@@ -122,7 +122,7 @@
     <dependency>
       <groupId>io.quarkiverse.oidc-proxy</groupId>
       <artifactId>quarkus-oidc-proxy</artifactId>
-      <version>0.2.2</version>
+      <version>0.3.2</version>
     </dependency>
     <dependency>
       <groupId>io.quarkus</groupId>
diff --git a/examples/process-security/kie-service-2/pom.xml 
b/examples/process-security/kie-service-2/pom.xml
index efb6e4ca62b..758763a5349 100644
--- a/examples/process-security/kie-service-2/pom.xml
+++ b/examples/process-security/kie-service-2/pom.xml
@@ -122,7 +122,7 @@
     <dependency>
       <groupId>io.quarkiverse.oidc-proxy</groupId>
       <artifactId>quarkus-oidc-proxy</artifactId>
-      <version>0.2.2</version>
+      <version>0.3.2</version>
     </dependency>
     <dependency>
       <groupId>io.quarkus</groupId>


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to