ci: weekly scheduled dependency check#47
Merged
Conversation
Mondays 06:00 UTC, plus workflow_dispatch for manual runs. Calls _checks.yml so the suite stays identical to PR/main runs. On schedule failure, opens (or comments on) a tracking GitHub issue labelled scheduled-failure so dependency rot doesn't sit silent. cancel-in-progress: false on this concurrency group — unlike docs.yml, we want the scheduled run to finish even if another fires before it. Mirrors modern-di's pattern. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Summary
Adds
.github/workflows/scheduled.yml(Mondays 06:00 UTC +workflow_dispatch) which calls the same_checks.ymlthat PRs /mainpushes use. On schedule-triggered failure,.github/scripts/report-scheduled-failure.shopens a tracking issue labelledscheduled-failure(or comments on the existing open one) so dependency rot — a ruff/ty/pytest release breaking on its own, a Python 3.14 incompat surfacing, etc. — surfaces as a noticeable artifact rather than silent CI red later.Concurrency group is
scheduled-dep-checkwithcancel-in-progress: false— unlike the docs deploy, the scheduled run should finish even if another fires before it.Mirrors
modern-di's pattern verbatim.Test plan
mainworkflow's_checks.ymlshould still run on the diff).gh workflow run scheduled-dep-check --ref mainshould manually fire the scheduled workflow and run_checks.yml._checks.ymlis intentionally broken on a throwaway branch + cron-triggered (or simulated viaact/ a one-offworkflow_dispatchthat forces failure), the report-failure job opens ascheduled-failureissue; a second failure comments on the existing issue instead of opening a duplicate.🤖 Generated with Claude Code