workflow/autobump: stop relying on autobump.txt file

[botantony]

Important: Do not tick a checkbox if you haven’t performed its action. Honesty is indispensable for a smooth review process.

In the following questions <cask> is the token of the cask you're submitting.

After making any changes to a cask, existing or new, verify:

• The submission is for a stable version or documented exception.
• brew audit --cask --online <cask> is error-free.
• brew style --fix <cask> reports no offenses.

Additionally, if adding a new cask:

• Named the cask according to the token reference.
• Checked the cask was not already refused (add your cask's name to the end of the search field).
• brew audit --cask --new <cask> worked successfully.
• HOMEBREW_NO_INSTALL_FROM_API=1 brew install --cask <cask> worked successfully.
• brew uninstall --cask <cask> worked successfully.

---

[bevanjkay]

Does this still skip running brew bump on Casks that use the :extract_plist for livecheck?
If it does, we should probably skip them by default here (without having to add no_autobump! to all of them).

[botantony]

Can you think of other cases when we do not need to use autobump and can detect it automatically?

[krehel]

Yes, files with version :latest should be ignored - which includes a majority of the fonts distributed.

:extract_plist should be ignored (as it is today) because of the negative impact on CI time, though we've done a lot of cleanup in this space within the last year and made efforts specifically to evaluate if :extract_plist was needed. We drove the count of those files down significantly.

That said, it could be worth exploring a one time per day job for just :extract_plist and see if it causes problems.

FWIW, just running some quick point in time stats in the Casks dir shows 7480 Casks, and we can ignore 3090 of them for matching deprecate! | disable! | :extract_plist | version :latest

We're autobumping close to 1800 Casks, or about ~41% of eligible apps. At this point there are very few PR's for version bumps that aren't already autobumped. It is likely if an application is bumped within every few months, it is already included in the list, though as always there's probably some we haven't included. Meaning, if it's not included already it probably gets an update at most once or twice a year, or hasn't been updated in an extended period of time.

[bevanjkay]

@botantony Does anything further need to happen before we can try moving forward with this?
Any Cask that isn't in autobump.txt can't currently be bumped with brew bump or brew bump-cask-pr because after the related changes in Homebrew/brew they are being detected as "autobumped".

Example;

 ~  brew bump google-chrome
==> google-chrome
Cask is autobumped so will have bump PRs opened by BrewTestBot every ~3 hours.

The same applies for homebrew-core at the moment as well.

[botantony]

It should be good to go once Homebrew/brew#19910 is merged and some casks are excluded from autobump manually (if needed)

[bevanjkay]

@botantony There's also a CI failure in this PR that needs to be resolved before this can be merged.

[github-actions]

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.