[Feature request] provide version for latest&no_check casks #4770
Comments
|
Checking the latest version in such a way is unsustainable, as you might imagine. Every app will do it differently, and not all of them will provide such information in an easy to find manner. In addition, that could make something like upgrading (not yet implemented) immensely slow, as it would have to hit every website to check for a version, and do a comparison. The benefits and drawbacks of having all casks being versioned is already being discussed, though, so I’ll ask you to see this issue, where the conversation is taking place. |
|
Hi @twlz0ne! Thanks for your suggestion. I would like to add that there is a standard for this called Appcasts, and that we are in the process of adding support for it: #3105, #4412, #4646, #4648, #4674. However, not every app uses the standard. It seems we will cover about 1/3 of Casks with the implementation that we are working on. Checksumming the releases page might also work, but would be subject to false positives whenever somebody changed the CSS. |
|
Also, not to mention that most of the software in the Caskroom is not released via GitHub, nor is all software whose source code is available on GitHub uses the built-in releases system. If we wanted to check the most recent version of a GitHub project's release, I would suggest using the GitHub API instead, which is much more reliable. However, each user would be limited to 60 API calls an hour, which for most practical purposes, is reasonable, but I can see that being a problem when the user is bulk-installing apps, e.g. after getting a new computer or provisioning a new system. |
We can find the last version from release notes (or other where) , e.g:
and also can record the version when installing it.
The text was updated successfully, but these errors were encountered: