So, just to be clear, you have a patch definition and corresponding patch policy set up for an application that the Jamf Pro server does not recognize (yet) and it keeps downgrading the application? I assume also that this application is getting upgraded later to the new version, only to be downgraded again by Jamf. Are those all correct assumptions?
Or, is this more about how you get your JSS to recognize the new version? If so, there isn't anything you can do directly about that. Jamf has to update their definitions for the new releases, which they usually do within a small number of days after it's out.
If it's the first scenario, I recommend unchecking both the "Allow Downgrade" and "Patch Unknown Versions" options in the patch policy settings, as shown. Or maybe just one of them to start.
If you have either or both of those enabled, its likely downgrading the product and, maybe it's something like Google Chrome where it keeps updating itself later, so it keeps coming up as an unknown version.
Hopefully that helps? If I'm off the mark on what the issue is you're experiencing, maybe you can explain a little further.
I'm using this one
So I'm on the right version.
