Skip to content

[Bug]: Dispatched release checks do not satisfy required PR rulesets #17

Closed

Description

@jinxiao

Affected module or tool

Release preparation / required GitHub PR checks.

Version or commit

Merged automation at c882b3686aeaf2ababa524a4b2fd3d439b99fa5e; full-release preparation PR #16.

Environment

GitHub Actions with the built-in token; active main ruleset requiring three GitHub Actions status checks.

Minimal reproduction

Run Prepare release for all modules. Its explicit workflow_dispatch runs pass on the preparation head. Attempt to merge the generated PR.

Expected behavior

Required PR checks are associated with the PR and allow merging after success. Only relevant checks should run.

Actual behavior

GitHub rejects the merge with HTTP 405: 3 of 3 required status checks are expected, even though all dispatched jobs are green on the exact head. Native pull_request runs exist in action_required state and must be approved. Official GitHub guidance explicitly says workflow_dispatch job checks do not satisfy PR rulesets: https://docs.github.com/en/pull-requests/how-tos/merge-and-close-pull-requests/troubleshooting-required-status-checks .

For this publication, the native runs were approved through the Actions API and are being verified. Protection rules remain unchanged; no synthetic passing checks were posted.

Acceptance criteria or proposed fix

Replace preparation's duplicate dispatches with activation of the existing native pull_request runs for this repository, PR, and exact head. Wait for their asynchronous creation, approve action_required runs with Actions write permission where allowed, and clearly report a required maintainer approval if GitHub rejects automatic approval. Preserve native event association during failure recovery. Cover missing/deferred, pending, success, approval, failed-run recovery, and wrong-PR/source cases with offline regressions. Keep maintainer review/merge authorization, fork boundaries, existing checks, and publication gates intact. Update operational guidance and record hosted publication evidence after it exists.

Activity

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions