Add a required release packaging gate - #31
Merged
Merged
Conversation
AI-assisted implementation with Codex. Agent-Session: 01a0cc1f-6e05-7822-b066-68d47380e331
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
1 participant
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.
Run release packaging on every PR and add a
Release packaginggate requiring both platform builds, formula generation, and both Homebrew jobs to pass. The gate also fails when dependency jobs fail or are skipped, and removes path filters so every PR can report the required check.After merge, enable this check in main branch protection while retaining all existing checks and strict mode. The README edit remains separate in #30.
Validation: actionlint and git diff checks passed locally; platform checks run on this PR.
AI-assisted implementation with Codex.