Updated Renovate workflow cron offset and timeout#28196
Conversation
ref https://linear.app/ghost/issue/PLA-48 Two compounding issues seen on the first day of `0 * * * *`: - GH Actions consistently dropped top-of-hour scheduled ticks. Every even-hour UTC fire (00, 02, 04, 06, 08, 10) since the hourly cron landed was lost, leaving us at de-facto every-other-hour. The Actions docs specifically call out the start of every hour as the worst delivery window. Moving to `17 * * * *` puts us off the contended slot. - 30m runs were hitting `timeout-minutes: 30` with real work still in flight (rebases, lockfile maintenance across 29 open PRs). Bumped to 45 so the catch-up cycles can finish cleanly while the backlog drains; this can drop back to 30 once the queue is steady.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
WalkthroughThis PR adjusts the Renovate GitHub Actions workflow configuration in Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
ref https://linear.app/ghost/issue/PLA-48
Why
First day on
0 * * * *surfaced two issues:17 * * * *puts us off the contended slot.timeout-minutes: 30mid-rebase or mid-lockfile-maintenance across the current 29-PR backlog. Raising to 45 lets catch-up cycles finish; can drop back to 30 once the queue steadies.