Chromium -> Homebrew for MacOS

[GaryElshaw]

Is there any reason why the latest version hasn't hit Homebrew yet?

[networkException]

Different distributions get maintained by different people in their free time.

Also, the homebrew release is very much up to date: https://formulae.brew.sh/cask/eloston-chromium

[GaryElshaw]

Maybe i'm misunderstanding, and no shade. My current version is 96.0.4664.110, this last week was updated to be 97.0.4692.71 and i was just wondering if there is something going on with the build i'm not seeing. Wasn't trying to be a dick, honest.

[networkException]

Sorry if I sounded mean, that wasn't my intention at all. I hope you can get everything updated :)

[kramred]

Hello,
97.0.4692.71 should be the latest version for now. I had some trouble with GitHub Actions failing repeatedly for the arm64 builds so I changed the format of the release tag to allow builds started in parallel to finish with a release that is not blocking the other builds (except if they finish on the exact same second in time, where I estimated the probability to be low enough to take that risk)
So maybe the maintainer of the brew cask code (who is not me) had to make some adjustments too.

[kramred]

This may be related to the error messages from brew. See the cask code on github, which shows the current version.

I think you have to fix your brew issues/errors first then it should work.

You can also download and install the current version manually till you've done that.

[GaryElshaw]

Thank you, I think you just verified an uninstall and reinstall of homebrew is necessary. I've tried 'brew doctor' but the complaints are largely python related, which i was expecting, but not the casks. Thanks again.

[GaryElshaw]

Uninstalled, reinstalled Homebrew, and still the same version. Interestingly, the errors are still there.

Running brew update --preinstall...
error: feeding unmodified Casks/stand.rb to diffcore
error: cannot rebase: Your index contains uncommitted changes.
error: Please commit or stash them.

[kramred]

Try asking in the brew community about that error, they may be of more use in finding a way to fix this.

[GaryElshaw]

Thanks!