Changelog

The changelog is your public "what's new" feed. Each entry is short, dated, and (optionally) linked to the original feedback post.

When to use the changelog

• Every release. Make it routine. Customers love being told what changed.
• Big features only. If your release notes are usually internal-detail-heavy, the changelog is for the user-facing summary.
• Don't overuse. "Fixed a typo" doesn't need a changelog entry. Bundle small fixes weekly.

Writing an entry

Dashboard -> Changelog -> New entry. Each entry has:

• Title - short and active. "Dark mode" beats "We've added a new theme option".
• Body - Markdown. Include screenshots; they make the page scannable. Flip Preview to see it the way customers will.
• Version (optional) - v2.4, 2026-04-29, whatever you use.
• Status - Draft, Published, Scheduled.
• Linked posts - pick the original feedback posts this entry resolves. Linked posts can be auto-marked Shipped.

Draft from GitHub

If the week's work already lives in git, skip the blank page.

GitHub drafts are on Startup and Scale (not Growth).

1. Connect a repo at Dashboard -> Integrations (/en/dashboard/integrations) -> GitHub.
2. Open Dashboard -> Changelog -> Draft from GitHub.
3. Pick since last published changelog or a date range.
4. Stay on the page. Drafting can take a minute or two. Feedjolt opens one draft - title plus customer-facing bullets, not a commit dump.
5. Flip Preview, edit, then Publish. Emails and webhooks wait until you publish.

Feedjolt does not watch the repo. There is no timer and no merge webhook. You click Draft from GitHub when you want a draft - usually after a release or once a week. Since last published covers everything merged since the last public entry.

To use another repo, pick it on Integrations -> GitHub and save. Disconnect only if you need a different GitHub account.

Staff see which commits and pull requests were used. The public changelog does not. Feedjolt does not auto-publish. This is not GitHub Issues sync.

See GitHub changelog drafts.

Promote a post to a changelog entry

When a post moves to "Shipped":

1. Promote to changelog appears on the post detail page.
2. Click it.
3. The title, body, and link are pre-filled. Edit, save, publish.

This is the fastest path: customer gets the "Your post shipped!" notification AND your changelog stays current.

Drafts and scheduling

Save as draft to come back later. Schedule for a future date if your release is on Tuesday but you're writing the entry on Friday.

Drafts and scheduled entries are not visible on the public changelog.

RSS

The changelog has an RSS feed at feedjolt.com/p/{slug}/changelog/rss. Customers can subscribe.

In-app notifications

When a customer who's voted on a linked post sees the changelog, they get a small "1 new" badge on the page. Optional email: configure at Settings -> Notifications -> changelog.published.