Update brew version to 1.31.0

[brzzdev]

SPM has picked up the latest release of 1.31.0 and is giving deprecation warnings, but there has been no update to the brew version in order to fix these.

I think based on the git history that this requires a manual bump.

Should this not be done on release of a new version, if you're going to list homebrew as a viable installation method in the README?

[thomasvl]

I think the brew support (and README reference) might all have been contributions, I don't know that anyone that can do releases here also can make updates for brew. That the "git history" link you provided makes it sorta look like maybe brew auto updates with some lag?

@FranzBusch @gjcairo @glbrntt – you all might know more about brew support.

[brzzdev]

Thanks for the prompt reply.
Looking again, you might be right about it auto-updating with some delay…

I saw the people included in the commit description alongside the bot for some of them, but then this one seems like it successfully bumped with no human intervention.

Perhaps the key is just for me to be a little more patient 😅

[glbrntt]

That the "git history" link you provided makes it sorta look like maybe brew auto updates with some lag?

That's my understanding of it too.

The last PR to update the swift-protobuf version hints that you might be able to give it a nudge: Homebrew/homebrew-core#225023

---

FWIW: in gRPC Swift we generally recommend avoiding the plugins installed via homebrew because it's easy to run into situations like this (or the other way around where the plugin is newer than your runtime version).

If you have a package with a dependency on SwiftProtobuf you can build protoc-gen-swift with swift build --product protoc-gen-swift. You can then specify the path to it when you invoke protoc: protoc --plugin=/path/to/your-package/.build/debug/protoc-gen-swift ....

[thomasvl]

Looks like it still hasn't updated, I wonder if the new artifact being in the releases feed it tripping the bot up in some way?

[thomasvl]

Looks like it still hasn't updated, I wonder if the new artifact being in the releases feed it tripping the bot up in some way?

I guess it could also be the tag that got created with that release that might cause issues?

Anyway, someone that knows more about brew will likely have to step in.

[brzzdev]

Brew is now up-to-date