Deployed version $n+1 versions older than retention depth, what happens?

[JustAnotherUser]

I think this is probably a dumb question but I'm going to ask it anyway.

Let's say an app is setup to create a new application + retain 1 old version. For simplicity we'll say the org is currently deploying 1.0. PMPC sees and creates 1.1, but we do not deploy it for whatever reason. PMPC sees 1.2 and creates the application.

We are now deploying a version one iteration older than what PMPC has been asked to maintain.

I'm assuming there's a sanity check in there to not delete applications currently deployed, but I'd like to confirm that's the case and I also don't want to re-break my retention/catalog.

Oh and follow up question:
How badly will I break things if I delete retained versions? Same example, but I delete 1.1 from SCCM before (or after) 1.2 is released? I don't plan to do this---just curious.

Thanks!

[Michael (Patch My PC)]

Yes, be default we won't delete Application with a Deployment. You can modify this setting at the Global Level here:
https://patchmypc.com/base-install-update-options-explained#topic4


Or from the Right-Click Menu option of the Vendor/Product Level
https://patchmypc.com/custom-options-available-for-third-party-updates-and-applications#new-application