New Definition Version on deployment despite no changes

Hi,

our Camunda Engine is embedded in a Spring Boot application.
Whenever we deploy this application anew due to our CI/CD-Chain, the engine will (on startup) redeploy the process models on the build path, creating new Definition Versions. We´re now on Definition Version 140 despite only having made 30 changes (we use a version tag to document changes so we know that for sure).
This is quite irritating and I feel like this is not the default behaviour.

Is there some configuration that we accidentally enabled and may disable?

Thanks in advance,
Ben F

Hello @Ben_F ,

you can find the solution for your problem here:

Hope this helps

Jonathan