Releases: Aldaviva/GamesDoneQuickCalendarFactory
Releases · Aldaviva/GamesDoneQuickCalendarFactory
2.6.0
2.5.0
- #16: Exclude fake runs like sleeping and pre-shows
- Target .NET 8.0 because 7.0 is out of support now
- Restart systemd service if it crashes
- Minor memory usage reduction when serializing lists of strings
- Removed response caching, which was redundant with output caching
- Increased client and server-side cache duration from 1 minute to 3
- Exclude runs in which annoying people are participating, can be disabled with optional query parameter
?includeAnnoyingPeople=true
- Send GDQ API requests to
tracker.gamesdonequick.com
hostname instead ofgamesdonequick.com
for presumably less load-balancer proxying
2.4.0
2.3.0
2.2.1
2.2.0
2.1.2
2.1.1
2.1.0
- #2: Added reminders when a GDQ event is about to start (1 week, 1 day, and 15 minutes before the pre-show starts)
- Added subscription instructions for Vivaldi, Mozilla Thunderbird, and Apple Calendar
- Removed event
Organizer
field to fix (helpful, easy to find) warnings in Outlook for Windows and silent errors in Thunderbird (resulting in no events appearing)- My MacBook Pro's antivirus was silently blocking executions of Thunderbird
- Thunderbird is incapable permanently add TLS exceptions, even when the Permanent checkbox is checked
- Fiddler was unable to make any TLS connections due to mysterious errors on an up-to-date, clean Windows 10 22H2 installation with no proxies, an accurate clock, untouched trusted root CA store, and default SChannel and cipher suite settings
- Figured out out how to view Thunderbird logs and HTTP traffic (Tools › Developer Tools › Developer Toolbox)
- Added automated tests
2.0.0
Previously, this was a console program that wrote an ICS file to disk and was run like a static site generator by a GitHub Actions workflow with cron schedules.
Now, it has been converted into an ASP.NET Core web application that regenerates the ICS on each request (with caching) to be reverse-proxied by Apache.
This change was made because the GDQ dates change too much every year to be covered by cron jobs. For example, SGDQ 2022 started in June, but SGDQ 2023 is starting in May, and running the cron job frequently year-round is silly.