Production analytics tracking was updated by removing the previous tracking script after confirming the new tracking setup was working. This helps ensure site analytics continue to record visits reliably without loading an extra tracking script.

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.

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 removes third-party tracking and feedback scripts from the app and error pages, reducing external requests and tightening the set of allowed connections. It also avoids reporting transient GitHub server errors as alerts, keeping issue reporting focused on problems that need attention.

Analytics tracking has been switched from Fullres to Umami in production, and the extra inline click tracking on key onboarding and sign-in buttons has been removed. This keeps measurement in place while making user interactions feel a bit cleaner across the dashboard and marketing pages.

Changelog view stats are now migrated when a repo is re-added and entries are moved to a new project. If the same date exists in both the old and new project, the counts are combined so your historical totals stay accurate instead of being split or lost.