The view-count correction task now stops early if given a cutoff time in the future. This prevents accidentally re-processing rows that were already written correctly after the fix went live, avoiding incorrect double-decrements and protecting your view-count data from being pushed in the wrong direction.

Custom domain verification is now safer and less likely to take a verified changelog offline during transient DNS issues. Exports are also more resilient, preventing jobs from getting stuck in processing. Analytics are more accurate going forward by fixing a view-count double-count on the first view of the day.

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.

Suspended GitHub App installations are now treated as an expected state, so affected installations and projects are marked inaccessible and disabled without generating noisy error reports. This release also includes security fixes for known dependency advisories, reducing risk in areas that process and sanitize user-facing content.

If a connected GitHub App installation has been removed, sync and repository fetching now treat it as no longer accessible instead of failing unexpectedly. This helps keep your connected projects in a consistent state by automatically disabling access when GitHub reports the installation is gone.