Updated our public notes to clarify how the release hook can time out on long requests, and what happens if a client retries while the first request is still running. This helps explain why duplicate entries could appear in rare cases and how the system responds to prevent that going forward.

Release hook requests are now less likely to create duplicate changelog entries when a client retries a slow request. You will also see clearer error messages when an entry cannot be updated or restored, and skipped releases no longer count toward monthly usage.

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.