Repository navigation
ci: cut the hub's scheduled cadence - #92
Merged
Merged
Conversation
The five hub schedules fired four times an hour each (two for descriptions), about 18 runs an hour on the release class, mostly with nothing to do. Their event paths already carry the work: producers dispatch on release, the receipts callback repairs dropped notifications, the finalizer runs as a workflow_call after publication and on facts changes, and the facts workflows run on push. The cron is only the safety net, so it moves to the cadence that net needs. workflow_dispatch stays on all five. - release-reconcile: every 15 minutes -> hourly (11 * * * *) - release-finalize: every 15 minutes -> hourly (3 * * * *); it already exits in seconds when no candidate waits - release-receipts: every 15 minutes -> every 30 minutes (1,31 * * * *), the existing overdue threshold of 30 minutes - facts-descriptions: twice an hour -> daily (17 3 * * *); a push on facts/** stays the primary path - facts-fanout: every 15 minutes -> daily (7 3 * * *); same reason tests/test_facts_fanout.py pins the new fan-out cron. docs/release-chain.md states the new cadence. These schedules stay disabled (bulletin #950) until laneboss's cross-run fix is live and the runner hook accepts them; this change can merge before that. Removed text: > `release-reconcile.yml` wakes every 15 minutes or manually. > as a reusable job after publication, on facts-file changes, every 15 minutes, > `release-receipts.yml` polls selected consumers every 15 minutes and accepts the Co-Authored-By: Claude Sonnet 5.5 <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.
Cuts the cadence of the hub's five scheduled workflows (CI-NOISE: they fail every scheduled run today at the release runner's pre-job hook and are disabled; this lowers the run count once they come back).
11 * * * *)3 * * * *); exits fast when no candidate waits1,31 * * * *)17 3 * * *); the push onfacts/**stays the primary path7 3 * * *); the push onfacts/facts.jsonstays the primary pathworkflow_dispatch, push and callback triggers are unchanged.tests/test_facts_fanout.pyfollows the new fan-out cron;docs/release-chain.mdupdated (three sentences).The five workflows stay disabled until the runner hook admits scheduled runs on main and the cross-run fix is live (#950/#974). Merging this changes nothing while they are disabled.
🤖 Generated with Claude Code