notefeed 0.12.0

Released 2026-10-13 · on GitHub

v0.12.0: /health also checks the image store, a terms page, and licenses per feed for the hosted service

Nothing to do when upgrading: without new settings an instance behaves as before, except for the two points under "Read before upgrading".

Read before upgrading

/health can now answer 503 because of the image store: with NOTEFEED_IMAGES set to fs or s3, the check also asks that store (a folder read, or one listing of at most one object, capped at 3 seconds). An instance whose bucket or keys are wrong was ok before and is unavailable now. With S3 billed per request, a probe every 30 seconds is about 2,900 listings a day.
terms and license are reserved feed names: posting to them answers 400. A feed that already has one of these names is no longer reachable under it.

For operators

/health says which part failed: the body gains checks (storage, images), each ok or unavailable. See Health check.
A terms page: NOTEFEED_TERMS_FILE names a Markdown file shown at /terms and linked in the footer, next to the imprint and the privacy page. See Imprint, privacy page and terms.

Hosted service

Licenses per feed (ADR 0029): the server can now tell a licensed feed from a free one. This is for notefeed.me and is off unless a payment provider is configured; a self-hosted instance has no limits and nothing changes for it.

API and clients

A new answer 402 license_required on posting a note, editing a note and changing the feed password, only on an instance that sells licenses. The OpenAPI description and the JS and Python clients are regenerated for it; the client packages are otherwise unchanged and take the version of the release.

Pull requests

13 Oct 2026, 21:33Report