Changelog
Project name, a large version number, date and up to three change lines.
The changelog template shows what shipped. A product name, a version label and a short list of changes are laid out like a release note, so the link to your changelog or release page previews the actual contents instead of a generic title.
The card shows up to three change lines of up to 80 characters each. Short, concrete lines such as a fixed bug, a new endpoint or a faster build read best, and they give people a reason to open the post. Because the list is an array field, it is sent as a JSON array in a POST request, or as bracket-indexed keys when you build a GET URL.
It fits release pages generated by your CI pipeline: render the card in the same job that publishes the notes, and attach it to the release, the docs page and the announcement post. Teams use it for weekly updates, versioned library releases and public roadmap posts alike.
- Versioned release notes
- Weekly product updates
- Library and SDK releases
- Public roadmap posts
Related: Quickstart · API reference · ogmake changelog
Parameters
| Parameter | Type | Required | Limit |
|---|---|---|---|
project | string | Yes | up to 120 characters |
version | string | Yes | up to 120 characters |
date | string | Yes | up to 120 characters |
changes | array of strings | Yes | up to 6 items of 80 characters |
Try it
POST /v1/images, Bearer-authenticated, with this template id and
params — see the quickstart for how to get a key, and for a
signed-URL example that links straight to a cacheable, cache-forever image URL without a
server round trip.
curl https://ogmake.com/v1/images \
-H "Authorization: Bearer og_live_..." \
-H "Content-Type: application/json" \
-d '{
"template": "changelog",
"params": {
"project": "Kitepath",
"version": "v0.4.2",
"date": "Sep 19, 2026",
"changes": [
"Added a retry queue",
"Fixed a race in the router cache",
"Improved cold start time"
]
}
}'
This template requires an array field (changes)
— over a GET route (Public URLs, Signing)
it's carried as bracket-indexed query keys instead of a JSON array; see the reference's "Array fields on GET routes".
A working public-URL example (mint a real key in the dashboard to replace {your-public-key}):
GET https://ogmake.com/p/{your-public-key}/changelog?project=Kitepath&version=v0.4.2&date=Sep+19%2C+2026&changes%5B0%5D=Added+a+retry+queue&changes%5B1%5D=Fixed+a+race+in+the+router+cache&changes%5B2%5D=Improved+cold+start+time
