Changelog

AuthHero ships continuously. Every Monday this page gains an entry for the week just ended: the handful of changes that alter how you run or integrate AuthHero, written out in full, and a complete accounting of everything else that landed.

Weeks are listed in the sidebar, newest first.

What this is not

It is not the package changelogs. Every published package carries its own CHANGELOG.md, generated by changesets from the changeset each PR declares. Those answer a precise, narrow question — what changed in authhero between 9.9.0 and 9.9.1 — and they answer it per package, in isolation, which is exactly what you want when a version bump breaks your build.

This answers a different one: what happened, and does it change how I run or integrate AuthHero? A single week's work usually crosses the core package, an adapter or two, the admin app and the widget at once, and no per-package changelog can show you that shape. Each entry closes with the version spans the week produced, so the two views meet.

It is not release notes. An entry says plainly when behaviour changes — a default that flipped, an endpoint that answers differently, a setting that moved — rather than phrasing a break as a feature.

How an entry is put together

Highlights are written, not generated. A digest is an editorial act, and no producer could re-emit prose, so the entries carry no "generated" marker.

What is mechanical is completeness. node tools/changelog-week.mjs --check reads each entry's declared range, walks git log for the merges inside it, and fails if any merged pull request is not named in the entry (a commit pushed without a PR has no number to name, so it is reported for the author to cover, not failed on). The prose names no pull requests — it is written for someone running AuthHero, who has no reason to open the repo — so each entry ends with a ledger of the merges it covers, in a comment that does not render. An author who drops a third of the week's merges produces a page that reads as finished and is not, and the only way to catch that by hand is to redo the work.