Repository navigation
chore: probe live providers weekly with failure issue - #19
Merged
Merged
Conversation
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
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.
Weekly proof the providers still answer (search, episodes, first-episode resolve) against the real network. Runs Mondays 06:00 UTC plus manual dispatch, never on push/PR so flakes can't block merges. One retry absorbs transient stalls; a real outage files (or comments on) a single deduped issue.
Validation: YAML lint clean, actions pinned to SHAs like the publish job. The workflow itself can only dispatch from main, so I will manually dispatch it right after merge to prove it end to end.