ci: run the scheduled dependency check daily - #33
Merged
Merged
Conversation
lesnik512
force-pushed
the
ci/daily-scheduled-checks
branch
from
September 20, 2026 10:50
e93b571 to
61aa2c9
Compare
lesnik512
force-pushed
the
ci/daily-scheduled-checks
branch
from
September 20, 2026 10:52
61aa2c9 to
dadea14
Compare
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 dependency check ran on Mondays, so an upstream release that breaks
maincould sit undetected for up to a week and then surface on whichever pull request happened to run next. Daily bounds that window at a day and keeps the failure attributed to upstream, through the tracking issue, instead of to an unrelated PR.The minute is staggered across the 06:00 UTC hour, unique per repository across the organization. GitHub deprioritizes scheduled runs that pile up on the same minute, and this change would otherwise put every repo on the top of the hour at once.
report-scheduled-failure.shdescribed the run as "weekly" in the label description and in the issue body; both now say "scheduled". Repeat failures still comment on the single open issue rather than opening one per day.