Review & Publishing

Review before publishing is available on every plan. In your repository's Overview tab, find Review & publishing to choose how new changelogs are published.

• Publish immediately: turn off Review before publishing. New entries are published as soon as generation completes. This is the default.
• Manual approval only: turn on Review before publishing and turn off Auto-publish after 24 hours. New entries stay as drafts until you publish them.
• Review with a time limit: turn on both settings. Unpublished entries become eligible for automatic publishing 24 hours after generation and are published by a later scheduler run.

The 24-hour option is enabled by default when review is used. Editing a draft does not restart that timer. Turn it off if every update must wait for your approval.

When changing review settings, read the confirmation options: you can keep existing entries as they are or choose the offered bulk publish or unpublish action.

1. Open the repository's Changelogs tab and find the draft you want to review.
2. Open the entry to read it. Use Edit to make changes, then save them.
3. Select Publish when the update is ready. You can also select several entries to publish together.
4. In Sharing, enable Hosted URL visibility and open the public page to check the result. Only published entries appear to readers.

Publishing an entry and enabling access to its page are separate steps. A custom domain has its own visibility control; see the Sharing guide.

• Owner email: generation alerts can arrive while an entry is still a draft. They are separate from reader subscriptions.
• Discord and Slack: configured channels receive published updates, including entries published automatically at generation. Drafts wait until publication. Channel delivery requires Plus or higher.
• Reader email: on Plus or higher, confirmed subscribers receive new published updates, whether published immediately after generation, manually, or by the 24-hour option. Reader email is sent once per entry; editing, regenerating, or republishing it does not trigger another send.

When you use Publish All with a channel webhook configured, the confirmation can skip Discord and Slack. That choice does not mute email. Publishing a single entry does not offer that choice.

See Notifications for channel setup, preferences, and delivery troubleshooting.

Automatic CHANGELOG.md sync is separate: it can create a GitHub pull request containing a draft before that entry is published on KittyLog.

Choose Unpublish in the Changelogs tab to return an entry to a draft. It stays private until you explicitly publish it again, even if the 24-hour option is enabled or a background job refreshes its content.

Unpublishing does not recall emails, channel posts, or changes already sent to GitHub. Publishing the draft again can send another round of owner or channel notifications. Reader subscription emails are not resent.

Editing or regenerating an already published entry keeps it published. Unpublish it first if you need to review the changes privately.