We added Runlight tracking alongside the existing Umami setup in production. This helps us better understand how the site is being used so we can make more informed product decisions while keeping analytics loading smoothly.

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.

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.

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.

This release patches a security issue affecting Active Storage variant processing and strengthens GitHub webhook handling during reinstall scenarios. Public endpoints now resolve owner and repo slugs even when URL casing differs, and private repositories added via webhook default to drafts to avoid accidental publishing.

This release fixes two GitHub-related issues that could block onboarding. Signups no longer fail when GitHub does not provide an email address, and GitHub App install updates no longer break when a single repository in the payload cannot be processed, helping ensure the rest of your repos still get connected.