Requests that included a forged Client-IP header could trigger an unhandled error and return a plain 500 response, bypassing normal protections. This release drops that untrusted header so requests are handled normally, keeping error responses consistent and reducing noisy, unauthenticated failures.

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 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.

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.

This release updates several underlying components in response to security advisories. You do not need to take any action, but you should benefit from a safer, more secure experience through updated third party libraries.