The main changelog route is the canonical public update feed.
Features, UX updates, and operational improvements appear there.
Use subscription flows when you want release updates delivered to you.
Use the repo and docs when you need longer-lived historical context.
Recent product themes
These entries summarize the recent direction of the product so you can see the kinds of changes that are being shipped without reading every release note in full first.
What the changelog is for
The changelog matters because it tells you what changed in the product contract: new surfaces, workflow refinements, billing changes, challenge-system additions, or fixes that alter how a route should be used.
Where to follow updates
The right release channel depends on how closely you follow the product. Use the public changelog for regular review, and use the docs or GitHub releases when you need supporting historical context.
How to interpret a release
Read a release note by asking what changed for the operator: did a new route appear, did a workflow simplify, did a billing or auth assumption move, or did a challenge or tool surface become more capable? That framing makes the changelog far more useful than reading it as generic marketing copy.