Keeping the homebrew formula up to date

[zeke]

brew install cog is a thing now! See https://github.com/replicate/cog/pull/849 and https://github.com/Homebrew/homebrew-core/pull/117929

It looks like it's pinned at 0,5.1. How should we go about keeping that up to date as we release new versions of Cog? My guess at a couple options:

• We bump that number whenever we do a release. Does that mean opening a PR on homebrew-core each time? 😬
• We point it at a tarball off the main branch, then promise ourselves to keep main stable. Then we'd never have to update the formula. Too yolo maybe?

[zeke]

cc @mattt

[mattt]

@zeke Honestly, I'm still a bit confused about what the expectations for contributors are after a formula is accepted.

Looking at open PRs, I'm noticing that a small set of users are contributing updates and they all seem to use brew bump-formula-pr. But looking at repos associated with core formulas, I'm getting mixed signals:

• The mitmproxy release docs says "The Homebrew maintainers are typically very fast and detect our new relese within a day" but also provides instructions for submitting a PR manually with brew bump-formula-pr.
• The release workflow for moodmosaic/clarinet has an explicit step for running brew bump-formula-pr.
• The GitHub CLI has a release workflow that uses what looks like an unrelated workflow (mislav/bump-homebrew-formula-action) to automatically open a PR to homebrew-core.

Based on this, I propose that we do the following:

• [x] Sit back and observe what happens on the next release, so long as it's a patch release. If the homebrew-core maintainers track releases and automatically update the cog formula within a reasonable timeframe, then we're all set.
  • [x] If we decide that we want to manage formula updates ourselves, we can add a step in our release workflow to use brew bump-formula-pr.
  • [x] If we release a new major or minor version before making a decision, we can run brew bump-formula-pr manually as a one-off.

Sound good?

[zeke]

Sounds like a plan 👍🏼

[mattt]

@zeke @nickstenning @evilstreak I saw that we just released 0.6.0, which includes a fix for an issue with CUDA base images. Is everyone on board with the plan to see if/when homebrew-core updates the cog formula? Or are the changes in this version important enough to merit a manual override?

[nickstenning]

Unfortunately in this case cog<0.6.0 is likely to be completely broken for everyone thanks to those Interesting Decisions:tm: made at nvidia.

That said, I doubt that hordes of people are already relying on homebrew for cog, so I'm ok with us waiting if we want.

[mattt]

@zeke @nickstenning The cog formula was bumped to 0.6.1 two days ago by a homebrew-core maintainer, which was two days after the version was released. So it looks like there's a reasonable expectation of eventual consistency, on the order of a few days. 😃

[zeke]

The cog formula was bumped to 0.6.1 two days ago by a homebrew-core maintainer,

Nice! Let's call this done then, and revisit if we ever need to.