Skip to content

Changelog

Ship it.Share the story.

Public or private. Embed, widget, or portal. Link the entry back to the post that asked for it.

Create your changelog Book a demo

TRUSTED BY THE BEST

1,500+ teams ship products instead of roadmaps with FeatureOS.

“Pricing felt right. Product felt intuitive. They even built a new feature for us!”
Michael Eckstein, Product Marketing Manager at Buffer
4.1M end users on FeatureOS boards
86% customers over 3+ years with FeatureOS

The loop

How a changelog stays honest.

Write it. Date it. Show it. Tag the post that asked for it.

  1. Write. Draft the entry, or generate one from shipped posts. Labels, team credits, media, and a CTA if the update needs a next step.

  2. Publish. Go live now, or pick a date — it publishes at 12:00 AM UTC. Pin a featured entry to the top of the list.

  3. Notify. Portal, embed, or the in-app slide-over. A red indicator marks new updates from the last 7 days.

  4. Close. Tag the board post that asked for it. Voters see what landed instead of chasing a status email.

Visibility

Public for customers.Private when it has to be.

A public changelog on the portal for customers. A private one for org admins and team. Visibility is also per entry — everyone, or only the user segments you pick.

  • Public changelog on your portal
  • Private changelog for org admins and team
  • Public changelog on a private organization
  • Per-entry: everyone or specific segments
  • Share a single entry with one link

Capabilities

What you can actually do.

Write and schedule an entry, pick who sees it, then embed or slide it over the product.

Write

  • AI draft from posts
  • Auto-translate (21 languages)
  • Team credits
  • Attachments + FAQs
  • CTA buttons

Publish

  • Publish now
  • Schedule a date
  • Featured / pin
  • Labels
  • Link shipped posts

Reactions

  • Emoji reactions
  • Comments + moderation
  • Views + visitors
  • Guest vs user views

Share

  • Full embed
  • Single-entry embed
  • Label-filtered embed
  • Slide-over widget
  • New-update indicator

Get started

Get a changelog live.

Open the module, write an entry, pick who sees it, then share.

  1. 1

    Open Changelog

    1 min

    Turn the module on. Settings & Embed is where the public/private toggle and snippets live.

  2. 2

    Write or generate an entry

    5 min

    Draft it, or import posts and let the generator write a first pass. Add labels and credits.

  3. 3

    Pick who sees it

    1 min

    Module public or private. Per entry: everyone, or only the user segments you assign.

  4. 4

    Embed or drop the widget

    2 min

    Share the portal link, paste a full / single / label-filtered embed, or the slide-over snippet.

Release notes

Questions about changelog

What a changelog is, how visibility and embeds work, and how you publish it.

Have more questions?

Release notes are the product updates you publish after you ship — features, fixes, improvements. In FeatureOS they live in the Changelog module: a portal page, an embed, or an in-app slide-over, with entries you can link back to the feedback posts that asked for them.

Yes. A public changelog lives on your portal. A private one is limited to org admins and team members. A private organization can still make the changelog public while boards and roadmap stay private. Per entry you can show it to everyone or only to selected user segments.

Yes. Paste the full-changelog snippet from Settings & Embed, embed a single entry by slug, or filter the embed by label IDs. There is also a slide-over widget (left or right) you attach to a button.

Yes. The changelog widget opens as a slide-over from the left or right. Turn on the indicator to show a red badge when something new shipped in the last 7 days. Widget v3 can filter by label and how many entries to show.

Yes. Set a publish date on the entry and it goes live at 12:00 AM UTC that day. FeatureOS does not document minute-level scheduling — the date is the control.

Yes. Changelog supports 21 languages. Set a default, allowed, and fallback language, then Auto Translate a draft and publish each translation. If a language is missing, the fallback version is shown instead of an empty page.

Yes. Create labels (name + color) and attach them to an entry. Readers use them to scan, and embeds can be filtered to one or more label IDs. Pin a major ship with the Featured toggle so it stays at the top.

Yes. Readers can react with emoji. Comments are optional — turn them on in Changelog Settings and moderate from the post. You can also add FAQs and file attachments on an entry.

Yes. Tag the completed board post onto the entry so the people who voted see what shipped. The AI generator can also pull those posts in when you draft.

No documented blast-to-all-users from the Changelog module. Share a single entry with a link, show it in the widget or embed, or target it to user segments. Email is not a changelog publish action in Help.

Updated August 2026

Machine readable

Ask an AI about changelog

Open Claude, ChatGPT, or Perplexity pre-filled with a prompt that points the model at /release-notes.md, the machine-readable version of this page.

Research FeatureOS changelog with AI
View as Markdown

Release notes

Ship it. Then tell the people who asked.

Public for customers, private for the org. Entries stay tied to the posts that put them there.

Create your changelog Book a demo