From 27407e90708d0292a7405a51a98ff5f5e291c486 Mon Sep 17 00:00:00 2001 From: Elijah Ben Izzy Date: Mon, 11 May 2026 09:24:41 -0700 Subject: [PATCH] ci: drop release-validation from required status checks The Release Validation workflow still runs on every PR (and on release-candidate tag pushes) so failures show up in the checks UI, but it no longer gates merging. This unblocks docs/website-only PRs (like #771) that were stuck in BLOCKED state because GitHub's branch protection treats the path-filtered SKIPPED jobs as non-passing, even though Stefan's prior fix in a655edf2 intended SKIPPED to satisfy the requirement. Trade-off: a code PR can technically be merged with Release Validation failing, but the red X is highly visible in the PR UI, and the workflow still runs on every push to main and on RC tags. --- .asf.yaml | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/.asf.yaml b/.asf.yaml index 1c342d43..dafa8541 100644 --- a/.asf.yaml +++ b/.asf.yaml @@ -62,10 +62,12 @@ github: required_status_checks: # strict means "Require branches to be up to date before merging". strict: false - # contexts are the names of checks that must pass - contexts: - - "Release Validation / build-artifacts" - - "Release Validation / install-and-smoke (3.12)" + # No required contexts — the Release Validation workflow still runs on + # every PR (and on tags) so failures are visible in the checks UI, but + # we don't gate merging on it. Path-filtered docs/website PRs were + # getting permanently blocked because GitHub treats SKIPPED jobs as + # non-passing for required-status-checks. + contexts: [] required_pull_request_reviews: dismiss_stale_reviews: false require_code_owner_reviews: false