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

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.

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.

This release tightens security around exports and sign-in flows, and fixes a session expiry mismatch that could log you out earlier than expected. It also makes the changelog API more consistent by returning the correct public URLs and resolving projects by the same repo identifier used in links.

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.