feat: share the scheduled-failure report as a reusable workflow - #127
Merged
Merged
Conversation
This was referenced Oct 4, 2026
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.
Replaces the 26 per-repo copies of
.github/scripts/report-scheduled-failure.shwith one reusable workflow here:.github/workflows/report-scheduled-failure.yml.Why
The copies drifted. The "Likely cause" sentence lists dependency names, and each repo's copy edited its own list. Six of those lists named
typing-extensionsin a repo that doesn't depend on it: eof-fixer, db-retry, jwks-client, release-scope, semvertag and faststream-concurrent-aiokafka. The modern-di integrations carried the same stale entry until this week. Apart from that sentence, all 26 scripts are byte-identical, and so is every repo'sreport-failurejob.The new message is generic. It says a dependency or Python release broke the build and points at the linked run, which shows the failing job.
Relation to #95
#95 rejected a shared
_checks.ymlbecauseworkflow_callinputs are scalars, which forced service containers and env maps into strings. This workflow takes no inputs, which matches the shape #95's closing comment suggests if the idea is ever reopened. The only per-repo variation today is compose2pod's note that its integration and conformance jobs need podman and docker. That note is dropped: the linked run shows which job failed.Changes
.github/workflows/report-scheduled-failure.yml(on: workflow_call, no inputs). It has the same label, title and find-or-comment logic as the script. It setsGH_REPObecause it runs without a checkout, and it gets itsissues: writepermission from the caller.mainunpinned.links.ymlcomment that pointed at the per-repo script now points at the shared workflow.Each repo's job becomes:
Verification
scheduled.ymlwith the job above), linted both against a local copy of the shared workflow, which checks the call and permissions, and in the remoteuses:form.uv run pytestpasses (173 tests), and so doesmkdocs build --strict.report-scheduled-failure.yml@shared-scheduled-failure-reporton push: