Publish a Changelog Entry in Canny
Use Changelog → Create a new entry, describe the shipped change, link relevant posts and review publication notifications. A release note should explain a usable change rather than announce an unshipped promise.
Before you start: Have permission to manage the changelog and verified release information. Email subscription notifications require the relevant Pro or Business capability.
Worked example: Announce that workspace owners can export the audit log. Explain where the control is and who can use it, then link the matching request instead of every loosely related reporting post.
Step-by-step guide
Gather release evidence
Confirm the feature is available to the stated audience. Record any role or plan limits and a support link before writing the announcement.
Create the entry
Open Changelog and choose Create a new entry. Lead with the user’s new capability, then explain the path to use it.
Link the right posts
Associate only the feedback posts addressed by this release. Check that their scope matches the change actually delivered.
Apply useful labels
Choose labels that help readers filter entries. Keep a correction distinct from a new capability instead of tagging everything alike.
Review and publish
Preview the text and images, then choose the Notify subscribers setting deliberately. Publish after checking the audience and the subscriber control.
Common mistakes
Assuming every voter is a changelog subscriber
Changelog subscription emails and post-status notifications are separate mechanisms. Link posts for context without claiming an automatic audience equivalence.
Sources and verification
Based on product documentation checked on 2026-11-04. This is a documentation-based guide, not a hands-on benchmark. Features and availability can change.