Problem
The daily-changelog recurring schedule uses a fixed UTC cron (0 7 * * *), which maps to midnight PDT but will shift to 11:00 PM PST when daylight saving time ends in November 2026.
This means changelog entries generated during PST months will cover 11pm-to-11pm PT instead of midnight-to-midnight.
Options
- Two schedules — one for PDT (07:00 UTC, Mar-Nov) and one for PST (08:00 UTC, Nov-Mar), with manual swap or seasonal pause/resume
- Use 08:00 UTC — always covers midnight PST; during PDT the entry runs at 1am PT (1-hour delay but correct day boundary if the entry generation uses calendar-day boundaries rather than "24h ago")
- Timezone-aware scheduler — if the hub scheduler gains TZ-aware cron support, switch to
0 0 * * * America/Los_Angeles
Recommendation
Option 2 is simplest — run at 08:00 UTC year-round and ensure the changelog agent uses explicit PT date boundaries (YYYY-MM-DD 00:00:00 -0800 / -0700) rather than relative time. The 1-hour delay during PDT is acceptable.
Timeline
Needs attention before November 1, 2026 (DST ends November 1, 2026).
Related: PR #209, schedule ID 76d3a06a-97b7-4c41-aa89-7708e5489851
Problem
The
daily-changelogrecurring schedule uses a fixed UTC cron (0 7 * * *), which maps to midnight PDT but will shift to 11:00 PM PST when daylight saving time ends in November 2026.This means changelog entries generated during PST months will cover 11pm-to-11pm PT instead of midnight-to-midnight.
Options
0 0 * * * America/Los_AngelesRecommendation
Option 2 is simplest — run at 08:00 UTC year-round and ensure the changelog agent uses explicit PT date boundaries (
YYYY-MM-DD 00:00:00 -0800/-0700) rather than relative time. The 1-hour delay during PDT is acceptable.Timeline
Needs attention before November 1, 2026 (DST ends November 1, 2026).
Related: PR #209, schedule ID
76d3a06a-97b7-4c41-aa89-7708e5489851