Always take latest item in Sparkle strategy.

[reitermarkus]

• Have you followed the guidelines in our Contributing document?
• Have you checked to ensure there aren't other open Pull Requests for the same change?
• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your changes? Here's an example.
• Have you successfully run brew style with your changes locally?
• Have you successfully run brew typecheck with your changes locally?
• Have you successfully run brew tests with your changes locally?

---

The first item is not necessarily the latest, so sort the items by date first. Secondly, sort by version in case some versions were released at the same time.

Fixes breakage introduced by #11146.

[BrewTestBot]

Review period skipped due to critical label.

[Yann-R]

Thanx for the fix.
As a side-effect:

• will the fixed strategy for sparkle automatically select only among the compatible versions according to the sparkle:minimumSystemVersiontag? e.g. in https://updates.devmate.com/com.runtimesharks.dndme.xml
• or will it always select the latest item, compatible or not with the host performing the livecheck?

[reitermarkus]

It will always select the latest, ignoring the system version. The livecheck really shouldn't depend on the macOS version, in theory even running brew livecheck on Linux should yield the same version.

[Yann-R]

@reitermarkus

The livecheck really shouldn't depend on the macOS version

OK 👍
When brew livecheck raises a version clearly tagged as "uncompatible" with the host, it may be a bit frustrating for certain uses. But if it is so by design, no problem!
Thanks.