Since Homebrew 1.0.0 most Homebrew users (those who haven’t run a
HOMEBREW_DEVELOPER=1 which is ~99.9% based on analytics data) require tags
on the Homebrew/brew repository
in order to get new versions of Homebrew. There are a few steps in making a new
masterCI job (i.e. main jobs green or green after rerunning), and that you are confident there are no major regressions on the current
brew releaseto create a new draft release. For major or minor version bumps, pass
If this is a major or minor release (e.g. X.0.0 or X.Y.0) then there are a few more steps:
odisabledcode, make any
odisabled, uncomment any
# odeprecatedcode and add any new
odeprecationsthat are desired.
brew release [--major|--minor]as input but have the wording adjusted to be more human readable and explain not just what has changed but why.
Please do not manually create a release based on older commits on the
It’s very hard to judge whether these have been sufficiently tested by users or if they will
cause negative side-effects with the current state of Homebrew/homebrew-core.
If a new branch is needed ASAP but there are things on
master that cannot be released yet
(e.g. new deprecations and you want to make a patch release) then revert the relevant PRs,
follow the process above and then revert the reverted PRs to reapply them on