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.

You can now request access to the REST API from Settings (available on Pro and Team plans), use new API documentation, and work with new authenticated endpoints for reading your changelog data. This release also strengthens security around previews, webhooks, and project access, and prevents accidental overwrites when multiple people edit the same entry.

This release expands compatibility for GPT-5 models by routing GPT-5.x requests through the right API, helping summaries generate reliably as models evolve. It also addresses a security concern and reduces release-time failures by ensuring the app can start cleanly during updates.

This release tightens security for the embed subscribe endpoint by honoring each project's allowed domains, so subscription requests are only accepted from trusted origins. It also reduces noise from expected asset compilation errors, keeping monitoring focused on issues that matter.

In this release, we've streamlined the changelog functionality by removing the multi-environment tracking feature. This change simplifies the process for users, as all deployments will now be treated as production releases, enhancing usability and clarity.

In this release, we have made important adjustments to the way version numbers are determined within the changelog. By implementing semantic comparison, we ensure that version numbers are accurately assigned, even when entries are created out of order. This change helps prevent conflicts and maintain consistency in version tracking.