This release focuses on making automated releases more reliable and easier to manage when something goes wrong.
It also ensures your usage stays accurate when a release ends up being skipped.
More reliable release hooks
If a release hook request is retried, the system now avoids creating duplicate changelog entries for the same release. When a conflict does occur, the API responds with a clear version conflict instead of silently creating another entry.
Skip-changelog detection during release creation has also been streamlined, so the hook can proceed as soon as it finds a change that should be included.
Clearer errors and fairer usage counting
When updating a changelog entry fails in the UI, you will now see the specific validation error message, which makes it faster to understand what needs fixing.
Restoring a deleted entry now reports a clear reason if it cannot be restored, for example if it would conflict with an existing live entry.
If a release is skipped because all changes are marked to skip the changelog, the system now deletes the empty entry and returns the counted usage so skipped releases are not billed.