2.7.14

• When Google Calendar randomly decides to partially delete an appointment and refuses to create another one with the same iCal UID, even though the zombie event can't be deleted, automatically change the UID prefix and retry, instead of requiring a manual recompilation and redeployment. Persist state of new UID prefix to ./state.json.
• In the past, the run's display_name property was preferrable over name because it excluded useless prefixes like BONUS GAME 1- , which isn't part of the name of the game. However, starting in SGDQ 2025, display_name is empty, so this program must fall back to name in that case.

2.7.13

• PAX East 2025 has each last run of the day as a 20-hour overnight run with an 18-hour setup time, instead of just ending at the correct time

2.7.12

• Tolerate 404 responses from schedule redirection, because sometimes (2025-03-20) the next event (SGDQ 2025) doesn't have a schedule published, and the previous event (Frost Fatales 2025) is no longer where the schedule page redirects.

2.7.11

• Don't have a mix of hyphens and em dashes in run descriptions, consistently use em dashes.
• Switched to new, improved HTTP/URL builder.

2.7.10

• #34: Real runs with opener and finale tags are not appearing
  • Frost Fatales events are inconsistent with the way they tag runs opener or finale compared to the way GDQ and Back to Black events do it. In GDQ and BTB, those tags mean the first and last interstitial segments of an event, but in Frost Fatales they mean the first and last speedruns of an event, while the first interstitial is tagged kickoff and the last ("Finale!") has no tags at all.
  • Is it really an interstitial segment if nothing comes before it, so it's not between anything? Is there a better phrase for non-speedrun segment?

2.7.9

• Added game release year.
• Block runs tagged "kickoff".
• Don't attempt to deserialize unnecessary properties, in case they are malformed.

2.7.8

• Exclude appointments with the "preshow" tag

2.7.7

• Alarms for first run in event are supposed to trigger before it starts, not after.

2.7.6

• Block runs based on their tags, such as opener, checkpoint, recap, sleep, and finale. All existing blocking logic is retained (title, duration, runner IDs).

2.7.5

• Ensure at least a 1 minute gap between runs to prevent certain calendar UIs from rendering runs in a zipper pattern.