Filter: All Feature UI Bug Fix Backend Integration Security Frontend Content Documentation Analytics API Performance Accessibility Database security
October 03, 2026

Admin Email Alerts for CronWatch

Feature Integration Backend
CronWatch job alerts can now be emailed to admin recipients, in addition to existing alert destinations. Messages include the job name, alert title and details, optional triage notes, and a direct link to the CronWatch dashboard so issues can be reviewed quickly.
October 02, 2026

Dependency Refresh for Scheduled Jobs

Backend Bug Fix
This release updates the library used for monitoring scheduled tasks. While there are no visible UI changes, it helps keep scheduled job behavior aligned with the latest upstream fixes and compatibility updates.
October 02, 2026

Scheduled Job Monitoring with CronWatch

Feature Backend Integration
This release adds scheduled job monitoring so missed, failed, stuck, or slow runs can be detected automatically. Checks run on a regular cadence, and alerts can be sent to your existing error tracking setup so issues are easier to spot and act on.
September 20, 2026

More Reliable Repo Sync and Domains

Bug Fix Integration Backend
Repo syncing is now more resilient when a GitHub repo rename collides with an existing name, so one problematic repo will not block the rest from appearing or updating. Custom domain setup is also more dependable, with retries and a verification email that only sends once the domain is actually serving correctly.
September 17, 2026

Security Update for Export ZIPs

Security Backend
This release updates the ZIP export component to address CVE-2026-85396. Users benefit from stronger protection when generating ZIP files for exports, with no changes required to how exports are used.
September 13, 2026

Rejected invalid UTF-16 form submissions

Bug Fix Security Backend
Form submissions that declare an ASCII-incompatible charset (such as UTF-16 or UTF-32) no longer trigger unexpected server errors. These requests are now safely rejected with a 400 response, helping prevent anonymous scanners from causing hard-to-diagnose 500s during request parsing.