From bce580e744a733e451ebd1bf4f433a0a62e0f618 Mon Sep 17 00:00:00 2001 From: Eric J Date: Sun, 8 Nov 2026 13:45:04 -0800 Subject: [PATCH 1/2] Move the Renovate window to Thursday and Friday Eric often runs short of usage on Mondays catching up on dependency PRs, and has plenty left by the end of the week. So Renovate now opens the weekly batch on Thursday and Friday (`* * * * 4,5`, Los Angeles time), and a Claude run merges it on Saturday. Security fixes are unaffected: `vulnerabilityAlerts` keeps its empty schedule. The window is 48 hours, which keeps the org preset's rule that it be at least 24 hours wide: the hosted app runs every few hours on its own clock, and a narrow window misses its runs. Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01Kd6o1aFcJ4CmpGhDgPionn --- .github/renovate.json5 | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/.github/renovate.json5 b/.github/renovate.json5 index 5602f9ef..b14eb21a 100644 --- a/.github/renovate.json5 +++ b/.github/renovate.json5 @@ -32,7 +32,7 @@ // The org preset supplies what used to be spelled out here: config:recommended, // helpers:pinGitHubActionDigests, the America/Los_Angeles timezone, the - // weekly batch from noon Sunday to noon Monday, automerge:false, + // weekly batch on Thursday and Friday, automerge:false, // prConcurrentLimit/prHourlyLimit, dependencyDashboard, osvVulnerabilityAlerts, // the rule that security fixes skip the weekly window, and the github-actions // grouping. @@ -135,13 +135,13 @@ // these ever breaks the build in a way a targeted bump would not have, that is // the evidence to flip it, and this comment is where to record it. // - // The schedule is the preset's own window, noon Sunday to noon Monday, so the + // The schedule is the preset's own window, all of Thursday and Friday, so the // lockfile PR arrives with the rest of the weekly batch. It has to be written // out here because `lockFileMaintenance` brings a schedule of its own and does // not inherit the preset's. lockFileMaintenance: { enabled: true, - schedule: ["* 12-23 * * 0", "* 0-11 * * 1"], + schedule: ["* * * * 4,5"], }, // Rebase bot PRs as soon as `main` moves, not only on a conflict. The default, From 761d1f242a4c598c22c17e13c89e21db0bf40cb9 Mon Sep 17 00:00:00 2001 From: Eric J Date: Sun, 8 Nov 2026 16:44:22 -0800 Subject: [PATCH 2/2] CLAUDE.md: describe the Thursday-Friday Renovate window, not Monday morning Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01Kd6o1aFcJ4CmpGhDgPionn --- CLAUDE.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CLAUDE.md b/CLAUDE.md index 5bb3ce29..a90eeed4 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -292,7 +292,7 @@ Two related sources, for when the game binary is not the easiest thing to reach: Dependency updates are handled by **Renovate**, configured in `.github/renovate.json5`. It is JSON5 so the reasoning lives in comments beside each rule - the comments are load-bearing, not decoration. -- **Updates arrive as one weekly batch**, Monday morning `America/Los_Angeles`. Security fixes deliberately skip that window. To pull a run forward, tick the "trigger a request for Renovate to run again" checkbox on the dependency dashboard. +- **Updates arrive as one weekly batch.** Renovate may open them any time on Thursday or Friday, `America/Los_Angeles` - that is the window it is allowed to open PRs in, not a promised delivery time. A Claude run reads and merges the safe ones on Saturday. Security fixes deliberately skip that window. To pull a run forward, tick the "trigger a request for Renovate to run again" checkbox on the dependency dashboard. - **Nothing automerges.** `automerge: false` is global with no exceptions. A green CI run proves the repo is *consistent*, not that a bump is *correct* - and planner correctness lives in the snapshots, where a subtle output change surfaces as a snapshot diff to review rather than an obvious failure. - **There are deliberate holds.** Before "fixing" a version that looks stale, read the rule that holds it. Each carries its reason and the condition under which to revisit. - **The dependency dashboard issue is the live inventory** of everything held back, everything queued, and everything detected. It is a better place to look than reading manifests by hand.