Documentation changelog

Every change to these pages, newest first, read from git at build time rather than written by hand.

What changed on this site, and when. The list is read from the repository's own history when the site is built, so it cannot drift from what actually happened and nobody has to remember to update it.

This is not the API changelog

The API's compatibility rules, what counts as a breaking change and what we owe you when one happens, are on Versioning. The API is versioned by URL and these guides are not, which is a deliberate choice explained there. This page is the history of the documentation itself.

Recent changes

fix(assistant): keep the conversation, and stop mangling the prose (#32)774933d
feat: documentation assistant, and the docs as an MCP server (#29)e062b0b
feat: Vietnamese locale, documentation history, and roomier code blocks (#27)590d306
docs: lead with the catalogue, and set the type the way the brand says to (#25)40608e0
docs(sdk): the functions the package exports beside the client (#23)c3fa340
feat(docs): docs at the root, the full product API map, and backend + platform guides (#21)de02b0d
feat(docs): clearer interface, and the SEO the site was shipping without (#19)97f64f6
feat(docs): version the API reference, and state what versioning means (#17)ef24488
feat: the PULSE developer handbook, on Fumadocs, at developer.thepulseapi.com (#4)34a6829

Reading a page's own history

Every page carries the date it last changed at the foot of the page, beside a link to that one file's full commit history. That is the quickest way to answer "did this page say something different last month", which is usually the real question.

The pages are MDX files in content/docs, so the history is ordinary git: every revision, who made it, and what else changed in the same commit.

Last updated View change history

On this page