Meta tags:
description=Documentation for the missing package manager for macOS (or Linux).;

Headings (most frequently used words):

homebrew, documentation, releases,

Text of the page (most frequently used words):
the (20), homebrew (18), #release (11), and (9), are (8), brew (8), new (6), main (6), there (5), that (5), major (5), any (5), has (4), for (4), minor (4), code (4), branch (3), have (3), core (3), but (3), you (3), then (3), this (3), blog (3), post (3), not (2), create (2), based (2), whether (2), these (2), been (2), users (2), negative (2), with (2), current (2), state (2), make (2), revert (2), prs (2), merged (2), tweet (2), machomebrew (2), twitter (2), account (2), should (2), more (2), before (2), delete (2), pass (2), odeprecated (2), odisabled (2), few (2), steps (2), draft (2), run (2), job (2), green (2), least (2), pull (2), changes (2), hours (2), issues (2), releases (2), documentation (2), please, manually, older, commits, very, hard, judge, sufficiently, tested, they, will, cause, side, effects, needed, asap, things, cannot, released, yet, deprecations, want, patch, relevant, follow, process, above, reverted, reapply, them, consider, submit, other, sources, hacker, news, reddit, cons, comments, common, people, take, chance, complain, about, regardless, their, usage, pros, gets, wider, reach, user, feedback, when, shipped, yourself, retweet, credentials, 1password, write, notes, use, output, from, input, wording, adjusted, human, readable, explain, just, what, changed, why, 319, https, creating, tag, see, details, deprecation, lifecycle, deprecating, disabling, removing, also, command, argument, definitions, replacement, add, desired, odeprecations, uncomment, publish, github, version, bumps, respectively, ensure, confident, regressions, clear, jobs, after, rerunning, one, request, completed, successfully, happened, couple, ideally, check, anything, pressing, needs, fixed, next, fix, merge, discussions, forum, requests, since, most, those, who, haven, set, which, analytics, data, require, tags, order, receive, versions, making, repository, homebrew_developer, dev, cmd,

Text of the page (random words):
homebrew documentation releases homebrew documentation releases since homebrew 1 0 0 most homebrew users those who haven t run a dev cmd or set homebrew_developer 1 which is 99 9 based on analytics data require tags on the homebrew brew repository in order to receive new versions of homebrew there are a few steps in making a new homebrew release check if there is anything pressing that needs to be fixed or merged before the next release in homebrew brew pull requests homebrew brew issues homebrew homebrew core issues homebrew discussions forum if so fix and merge these changes ensure that no code changes have happened for at least a couple of hours ideally 4 hours at least one homebrew homebrew core pull request ci job has completed successfully the state of the homebrew brew main ci job is clear i e main jobs green or green after rerunning you are confident there are no major regressions on the current main branch run brew release to create a new draft release for major or minor version bumps pass major or minor respectively publish the draft release on github if this is a major or minor release e g x 0 0 or x y 0 then there are a few more steps before creating the tag you should delete any odisabled code make any odeprecated code odisabled uncomment any odeprecated code add any new odeprecations that are desired also delete any command argument definitions that pass replacement see deprecating disabling and removing for details on the deprecation lifecycle write up a release notes blog post for https brew sh e g brew sh 319 this should use the output from 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 when the release has shipped and the blog post has been merged tweet the blog post as the machomebrew twitter account or tweet it yourself and retweet it with the machomebrew twitter account credentials are in 1password consider whether to submit it to other sources e g hacker news reddit pros gets a wider reach and user feedback cons negative comments are common and people take this as a chance to complain about homebrew regardless of their usage please do not manually create a release based on older commits on the main branch 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 main 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 main