From 6fbcca68f216d1fa3e06f96c5ab6dded2bc0576b Mon Sep 17 00:00:00 2001 From: Sebastian Beltran Date: Mon, 15 Jun 2026 12:16:59 -0500 Subject: [PATCH] fix(meetings): align P4W schedule anchor to land on Jun 15 The 2026-05-16 change to a P4W (4-week) cadence kept the original anchor (2025-05-05), so the series landed on 2026-06-01 / 2026-06-29 and skipped the expected 2026-06-15 meeting. No agenda issue was created for it. Move the anchor to 2026-05-18 (4 weeks before 2026-06-15) so the 4-week series falls on 2026-06-15, 2026-07-13, ... while keeping the monthly cadence intact. Co-Authored-By: Claude Opus 4.8 (1M context) --- .github/workflows/generate-meeting-agendas.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/generate-meeting-agendas.yml b/.github/workflows/generate-meeting-agendas.yml index 74329d2..976b1e7 100644 --- a/.github/workflows/generate-meeting-agendas.yml +++ b/.github/workflows/generate-meeting-agendas.yml @@ -26,7 +26,7 @@ jobs: orgs: webpack,webpack-contrib agendaLabel: 'tsc-agenda' meetingLabels: 'meeting' - schedules: '2025-05-05T11:00:00.0[America/Chicago]/P4W' + schedules: '2026-05-18T11:00:00.0[America/Chicago]/P4W' createWithin: 'P7D' issueTemplate: 'meeting-agenda.md'