testflight 320

[exherb]

No description provided.

[rolandwalker]

Thanks!

Testing the new URL, I do not get version "320", but the same as the old URL: version 1.0_beta313.

[exherb]

Sorry, the version ("320') was extracted from CFBundleVersion at Info.plist of the newest testflight.app. I thought it's better for sparkle upgrade check in the future.

[rolandwalker]

Ah, yes, @exherb that is excellent thinking as well.

We have only recently added the :sha256 key to the appcast stanza (#6680, #6686). The next step will be to detect when the checksum changes, meaning that there is a new version.

Then we have to add code parse the appcast itself. Per this authoritative comment, sparkle is using the "320" number you proposed as its way to track the versioning (sparkle:version in the XML). But sparkle:shortVersionString is what is presented to the user.

In this case sparkle:shortVersionString is a yet-different value: "1.0".

I'm not sure how we will end up resolving this, because Casks ought to stay as simple as possible. We added the :latest_version key to appcast for some of this, but have left it undocumented so far — in part because I realized that :latest_version is easy to confuse with the already-existing version :latest.