Changelog entries
Build a changelog page from Update blocks, each with a label like a date or version and any content you like.
Updated Nov 19, 2026
<Update> is one entry in a changelog. Stack them on a page, newest first, and each one gets its own row with the label on the left and the notes on the right. On narrow screens the label sits above the notes.
March 2026
v2.4.0
Webhook retries
The Acme API now retries failed webhook deliveries.
- Up to five retries over 24 hours.
- Each retry sends an
Acme-Retry-Countheader.
February 2026
v2.3.0
Bulk user import
Create up to 1,000 users in one request with POST /users/bulk.
<Update label="March 2026" description="v2.4.0">
### Webhook retries
The Acme API now retries failed webhook deliveries.
- Up to five retries over 24 hours.
- Each retry sends an `Acme-Retry-Count` header.
</Update>
<Update label="February 2026" description="v2.3.0">
### Bulk user import
Create up to 1,000 users in one request with `POST /users/bulk`.
</Update>
On wider screens the label and description stay in view while you scroll through a long entry.
Props
| Prop | Type | Default | Description |
|---|---|---|---|
label | string | none | Shown as a pill, usually a date or version. |
description | string | none | Smaller text under the label. |
The content between the tags is the entry. It takes any Markdown or components: headings, lists, images, callouts.
Tips
- Give each entry a heading. Headings inside entries appear in the page's table of contents, so readers can jump to a release.
- Keep one changelog page and add new entries at the top.
- The visual editor shows
<Update>as read-only source and saves it back unchanged. Edit entries in source mode.