Skip to content

ci: fix release verification circular failures, issue spam, and new-component compliance - #9853

Open
bshaffer wants to merge 6 commits into
mainfrom
ci/release-verify-per-tag-issues
Open

bshaffer wants to merge 6 commits into
mainfrom
ci/release-verify-per-tag-issues

Conversation

@bshaffer

@bshaffer bshaffer commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

Fix circular failures, issue spam, and new-component repo compliance in release CI:

  • Remove release:verify from release.yml (Split and Release Components) and trigger release-verify.yaml via workflow_run once Release Components completes
  • Ignore Verify Releases and Split and Release Components check runs in ReleaseVerifyCommand so release:verify does not mark its own in-progress run PENDING or deadlock on main-dispatched runs attached to the release SHA
  • Update release-verify.yaml to append failure timestamps/runs to a table in a single open Release verification failed issue (without posting nightly comments) and auto-close it once verification passes
  • Skip the repo settings check in repo:compliance for new components (0.0.0 / 0.1.0 in CI), matching webhook and Packagist checks until repo:split disables pull requests on first release

@bshaffer
bshaffer requested a review from a team as a code owner November 17, 2026 00:15
@bshaffer bshaffer changed the title ci: track release verification failures per tag without repeated comments ci: fix release verification issue spam and new-component repo compliance Nov 17, 2026
@bshaffer bshaffer changed the title ci: fix release verification issue spam and new-component repo compliance ci: fix release verification issue noise and new-component repo compliance Nov 18, 2026
@bshaffer bshaffer changed the title ci: fix release verification issue noise and new-component repo compliance ci: fix release verification circular failures, issue spam, and new-component compliance Nov 18, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants