Auto-update doesn't work

[ferenc-a]

Output of brew config

The issue seems conceptual, has the exact same error message in two environmets, including one GitHub action CI agent, so I won't post the environment.

Output of brew doctor

.

Description of issue

How do I update my existing cask, and why do these methods not work, even tough they used to?
Neither does the manual method work nor did BrewTestBot open a new PR automatically, like the error said.

Our cask, kameleo had a successful auto-update PR after the first manual submit PR. However current attempts to auto-update don't work.

We use this GitHub action, which fails at this command. I also fail at this stage when trying to execute it manually, and the error message is really unhelpful.

/opt/homebrew/bin/brew bump-cask-pr --no-audit --no-browse --message=[`action-homebrew-bump-cask`](https://github.com/eugenesvk/action-homebrew-bump-cask) --version=4.2.0 homebrew/cask/kameleo

Error: Whoops, the kameleo cask has its version update
pull requests automatically opened by BrewTestBot every ~3 hours!
We'd still love your contributions, though, so try another one
that is excluded from autobump list (i.e. it has 'no_autobump!'
method or 'livecheck' block with 'skip'.)

Some related issues I found were also unhelpful: Homebrew/homebrew-cask#218095.

[botantony]

Homebrew can update most of the packages automatically, but it failed this time because of a failed audit: https://github.com/Homebrew/homebrew-cask/actions/runs/18936082613/job/54063172303#step:5:9359

Should be fixed in Homebrew/homebrew-cask#234403

[ferenc-a]

Thank you!
In case it's relevant: the updated package doesn't support Big Sur (11), which is currently on the kameleo.rb metadata. It only supports Monterey (12). I intended to bump it manually after the update.
Edit: I see, so that was the issue. Is the best practice for this case a manual requirements update PR, or a requirements + version update PR?

[botantony]

It is better to leave the updates to the bot, but in case when simply updating URL and checksum isn't enough, no one would be against fixing the cask manually

[ferenc-a]

So just open a discussion like this?
Also, is there some place where I could've figured out the issue? Run brew audit somehow on the future version? Or was looking at the CI logs the only clue for you?

[SMillerDev]

Just open a pull request where you manually change the values. Then CI will check if the audits etc are correct.