Semantic versioning of MKPs

Yes, but in either case you have to select the right package…

Fair point. Currently you can not do that. I still believe that this problem should not be solved by encoding some meta information into the MKP version number, but I agree that it would be nice to somehow “bundle” those packages. Maybe @baris.leenders has an idea?

The weird thing is that currently MKPs are built from a deployed copy of themselves, which prevents us from implementing other interesting options such as having files for different Checkmk versions in one single MKP.