so i've implemented two new checks to try to improve the situation there: but, it seems like there are quite a lot of casks WITH appcast that are outdated despite the appcast. percentage of entries in the txt files that are actually valid new releases). Ok, the cask-repair system for apps without appcast has been working quite well over the past month, i guess around 80% success rate (i.e. entries that are not real official releases of this app) here so i'll add them to the different filter-lists in the postprocessing script so that they won't appear in the next days output anymore. i think this would also be a good task to get started with contributing to HBC.įor the time being, it would be best to note false positives (i.e. So, long story short, basically it would be great if the community could have a look at theĮach day and look through them to see which of those entries are real, official new releases of the apps and submit cask-repairs accordingly. The design and implementation of the system is discussed here: #52837Īnd there was also a bit discussion about this here: every day the script finds around 5 - 10 outdated Casks that should be updated e.g. every day i let a script run that compares the version of the Casks without appcast, to the database of app-versions that our company maintains. Therefore i've been focusing my efforts on automatically finding outdated Casks on those without 'sparkle appcast'. (his system incidentally also works for non-sparkle appcasts, but currently most of the Casks that have no sparkle, also have no appcast-stanza) any Cask with a version number needs to be updated every time a new version of this app is released.įor apps that have an sparkle/rss or github/atom feed from the vendor, keeping them up-to-date is relatively straightforward. One of the 'problems' of Homebrew Cask is that it requires constant maintainance to keep working.

Bitwig studio 1.3.5 crack