Free tool

changelog templatesrendered as they will publish

5 templates for the releases most products ship, in plain markdown. Load one, make it yours, and the preview renders through the same parser, sanitiser and stylesheet as a published page, so what you see is the article.

Get a changelog to publish it to How the changelog works

Write and preview

Start from a template

Title

Saved views, and a sidebar that behaves

NewFixed

Rendered by the same server, the same sanitiser and the same stylesheet as a published entry, so this is the article, not an impression of it. Paste the markdown into your changelog editor, or on Pro send it through the API or the MCP server.

Changelog templates

Each one is a finished entry with the decisions already made: what goes first, how changes are grouped, where the request gets credited. Copy the markdown, or pick it above to edit it in the designer.

Weekly roundup

A steady cadence of small releases: one entry a week, headed by the change users will notice most.

# Saved views, and a sidebar that behaves

Two things this week, one of them overdue.

## Saved views

Filter the board however you like, then save it. The URL was always
shareable; now it has a name.

- Pin a view to your sidebar
- Share it with a teammate and they get your filters, not theirs

## Fixed

A long changelog entry could push the sidebar off a narrow screen. It
scrolls now, like everything else.

Versioned release

Libraries, APIs and apps with version numbers. Grouped the way Keep a Changelog groups a CHANGELOG.md file.

# v2.4.0

Released 3 November 2026. Upgrading from 2.3 needs no changes.

## Added

- CSV export for every report, from the **Export** menu
- `--json` flag on the CLI for machine-readable output

## Changed

- Search results load about twice as fast on large workspaces
- The default session length is now 30 days, up from 14

## Fixed

- Dates in exports used the server's time zone instead of yours
- The invite email could arrive without its sign-in link

Feature launch

One change big enough to carry an entry by itself: say what it does, who asked, and how to start.

# Recurring invoices are here

You asked for this one more than anything else on the board, so it gets
an entry of its own.

## What it does

Set an invoice to repeat weekly, monthly or yearly. Each one goes out on
schedule with the same line items, and you can pause or edit the series
at any time.

## How to start

1. Open any invoice and choose **Make recurring**
2. Pick how often, and when the first one goes out
3. Save. The next three dates appear under the invoice

## What's next

Card payments on recurring invoices are next. Vote on the request if
you want it sooner.

Fixes only

A maintenance release. Lead with the fix most people hit, and keep each line to what the user saw.

# Six fixes, one of them for a crash

A quiet week for features and a busy one for fixes.

- The app no longer crashes when you rename a file that is still uploading
- Keyboard shortcuts work again after switching workspaces
- Notification emails show the right workspace name
- Long project names no longer overlap the search box
- Exported PDFs keep their page breaks
- The billing page loads for accounts with more than 50 invoices

Breaking change

Anything that needs action from your users: say who is affected, what to do, and by when, before anything else.

# API v1 retires on 1 March 2027

**Who this affects:** anyone calling `/api/v1` directly. If you only use
the dashboard or the official SDKs, there is nothing to do.

## What changes

From 1 March 2027, requests to `/api/v1` return `410 Gone`. The v2
endpoints take the same fields and return the same shapes, plus
pagination on every list.

## What to do

1. Replace `/api/v1` with `/api/v2` in your base URL
2. Read `next_cursor` from list responses instead of `page`
3. Test against v2 now: both versions run side by side until March

> Questions? Reply to this entry's email and a person will answer.

What makes a changelog entry work

The templates follow five rules. They hold whether you publish here, in a CHANGELOG.md file, or anywhere else.

01
Lead with what the user can now do
“Export any report to CSV” beats “Refactored the export pipeline”. The internal change is your story; the new ability is theirs.
02
One date, and a version if you have one
People scan a changelog by time. A version number matters when users install or pin something; skip it when they don't.
03
Group by New, Improved and Fixed
Readers look for one kind of change at a time. Three fixed groups, used every time, make a long changelog easy to skim.
04
Say who has to act, first
A breaking change opens with who is affected and what to do by when. Everything else in the entry can wait.
05
Link the request it answers
If someone asked for it, link the request and tell them. A changelog that closes the loop gets read; one that doesn't gets ignored.

What renders

Headings, lists, links, bold and italic, inline code, fenced code with syntax highlighting, blockquotes, images and tables. HTML in the source is sanitised rather than trusted, here and on your public page, because both run the same code.

## What changed

- **Saved views**: filter, then save it
- Fixed a sidebar that could overflow on a phone

```bash
npm install feedfast-mcp
```

> Anything in here reads as a callout.

Getting it published

Paste the markdown into the editor in your dashboard. Or skip the dashboard on Pro: the REST API takes the same fields, and the MCP server lets your coding agent publish the entry as the last step of shipping the thing it describes.

# Pro: REST API key
curl -X POST https://feedfa.st/api/v1/projects/your-project/changelog \
  -H "Authorization: Bearer ff_your_key" \
  -H "Content-Type: application/json" \
  -d '{"title":"Saved views","tags":["New"],"contentMd":"…","publish":true}'

Published entries land on your hub page, your RSS feed and every embedded widget at once, and the What’s new badge lights up for everyone who hasn’t seen it. Comparing tools first? See the best changelog tools for SaaS.

Somewhere to publish it

A changelog page on your slug, an RSS feed and an embeddable widget, free for one project. The markdown you just wrote is ready to paste.

Start free See the changelog module