ci: harden Homebrew release validation - #34
Closed
huides00 wants to merge 2 commits into
Closed
Conversation
Use the Homebrew Formula API when resolving Core dependencies so the release job does not depend on a stale local Core checkout. Add a manual dry-run mode that exercises resource regeneration and formula validation without creating a tap pull request.
huides00
requested review from
Scoombe,
afercal and
siddhuwarrier
as code owners
September 1, 2026 13:37
Scoombe
approved these changes
Sep 2, 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.
Description
Homebrew release validation now resolves official Core dependencies through Homebrew’s Formula API instead of forcing a large local Core checkout, avoiding the inconsistent python@3.12 lookup seen in the release runner. A manual dry-run option exercises PyPI lookup, resource regeneration, and formula validation without creating or pushing a tap pull request, so the release path can be verified before merging.