chore(ci): use check-runs API for npm-publish CI gate#46
Merged
StefanSteiner merged 1 commit intoMay 27, 2026
Merged
Conversation
The previous polling logic queried the legacy commit-status API
(/commits/{sha}/status), which only returns checks reported via the
older Status API. GitHub Actions reports results as check-runs, not
statuses, so the poll returned state=pending forever even after CI
fully succeeded. Switch to the check-runs API and aggregate by
required check name, treating success/skipped/neutral as passing.
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 previous polling logic queried the legacy commit-status API (/commits/{sha}/status), which only returns checks reported via the older Status API. GitHub Actions reports results as check-runs, not statuses, so the poll returned state=pending forever even after CI fully succeeded. Switch to the check-runs API and aggregate by required check name, treating success/skipped/neutral as passing.