docs: clarify upstream lifecycle requests#22052
Merged
MikeMcQuaid merged 2 commits intomainfrom Apr 21, 2026
Merged
Conversation
- document that upstream requests or "broken" claims alone should not justify deprecating, disabling, or removing software - point maintainers to Homebrew signals such as analytics and user reports before taking lifecycle actions - keep the policy aligned across `docs/How-to-Create-and-Maintain-a-Tap.md`, `docs/Homebrew-homebrew-core-Maintainer-Guide.md`, and `docs/Homebrew-homebrew-cask-Maintainer-Guide.md`
Contributor
There was a problem hiding this comment.
Pull request overview
Clarifies Homebrew lifecycle policy that upstream requests (or unsubstantiated “broken” claims) alone shouldn’t drive deprecation/disable/removal decisions, and points maintainers toward Homebrew signals (analytics + user reports) before taking lifecycle actions.
Changes:
- Updated review dates across the three docs.
- Added explicit policy language in Tap documentation about upstream taps not being sufficient justification for lifecycle actions.
- Added parallel guidance to the core and cask maintainer guides to keep lifecycle decisions grounded in installs/user reports.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 5 comments.
| File | Description |
|---|---|
| docs/How-to-Create-and-Maintain-a-Tap.md | Adds upstream-request lifecycle guidance in the “Upstream taps” section; updates last_review_date. |
| docs/Homebrew-homebrew-core-Maintainer-Guide.md | Adds maintainer-facing lifecycle clarification for formulae; updates last_review_date. |
| docs/Homebrew-homebrew-cask-Maintainer-Guide.md | Adds a new lifecycle section for casks; updates last_review_date. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
carlocab
approved these changes
Apr 21, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
docs/How-to-Create-and-Maintain-a-Tap.md,docs/Homebrew-homebrew-core-Maintainer-Guide.md, anddocs/Homebrew-homebrew-cask-Maintainer-Guide.mdbrew lgtm(style, typechecking and tests) with your changes locally?Used OpenAI Codex with multiple reviews and edits.