Repository navigation
ci: run version updates at minute 17 instead of the top of the hour - #714
Merged
Merged
Conversation
GitHub delays and can drop scheduled workflows at the start of every hour under load. Over the last 100 scheduled runs the median gap was 4.7h instead of 1h, which delayed picking up Junie 3813.9 by ~2h.
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.
Summary
Move the
Update Agent Versionsschedule from0 * * * *to17 * * * *.GitHub documents that scheduled workflows can be delayed under load, that "high load times include the start of every hour", and that queued jobs may be dropped; it recommends scheduling "at a different time of the hour".
In practice the hourly schedule has been running far less often: across the last 100 scheduled runs (Oct 5–24) the median gap was 4.7h (min 1.8h, max 9.5h). On Oct 23 this delayed the Junie
3813.9GA release (published 10:17 UTC) until the next scheduled run at 12:15 UTC.An off-peak minute should reduce delays, but GitHub still gives no timing guarantee.
Changes
.github/workflows/update-versions.yml: cron0 * * * *->17 * * * *AGENTS.md: update the documented schedule