build(release): Add statusProvider
context check for craft
#8685
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.
To ensure we wait for the correct check to pass before continuing with publishing.
I think it is correct to use the "human readable" name of the check (??), at least the example looks similar. This is an example for what we are waiting for: https://github.com/getsentry/sentry-javascript/actions/runs/5715683859/job/15486522728
If I understand this correctly, this was completely broken and just looked for any (??) successful check..?!
See getsentry/craft#482