fix(ci): check live release prerequisites before merge - #5
Merged
Conversation
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.
The merged repair passed every package test and release fixture, but publication still failed because the live default branch is unprotected. The previous gate did not test that prerequisite before merge. Current main has exactly the previously tested PR tree, so this is not a rebase regression.
This change requires a read-only Release prerequisites job in the same reusable CI used by PRs and post-rebase releases. It verifies the dynamically selected default branch is protected and its effective rules require Package gate from GitHub Actions. The aggregate rejects any failed or skipped prerequisite. It adds 23 offline fixtures and removes the obsolete checked-in ruleset that required only PHP 8.5 on a hardcoded main branch.
This PR is deliberately a draft. Code does not activate repository settings, and the connected GitHub app cannot administer them. From any updated package checkout, an administrator must run:
These commands cover all thirteen package repositories. Apply settings first, then rerun PR checks and rebase only after the complete gate passes. Contents-only CI cannot inspect the immutable-release setting; the administrator audit remains required. Actual publication must then succeed and be verified as immutable.
Validation: all 23 new offline fixtures pass; existing package and release tests passed on the merged commit. This PR's live CI is expected to report the real unprotected-branch blocker until setup is applied. Runtime code, release versions, tags and published releases are unchanged.