What's new
docker pull ghcr.io/new-usemame/calibre-web-nextgen:v4.0.61
(or :latest if you track latest)
Browser tab + navbar now say "Calibre-Web NextGen" on existing installs (#191)
The v4.0.60 rebrand changed the default for fresh installs but left existing rows alone, so anyone who upgraded still saw Calibre-Web (if they came from stock CW) or Calibre-Web Automated (if they came from CWA) in the browser tab and the top-left navbar. v4.0.61 ships a one-time, idempotent migration that rebrands those two known legacy defaults on container startup. Custom titles (Maggie's Library, Coundou Family Library, etc.) are preserved — the migration only touches the two values that were the stock-default fork chain.
OPDS feed now emits <content> alongside <summary> (#195, reporter + author @droM4X)
Closes #190. Some OPDS readers (Readest reported in the issue) prefer to display <content> over <summary>. Per OPDS 1.2 §5.1.2 each entry now emits both: <summary type="text"> carrying the first sentence as a quick preview, <content type="text"> carrying the full description. Verified live against a 42-description test library — both tags render, the XML still parses cleanly, no client breakage.
Container healthcheck actually checks the database (#197, inspired-by @droM4X via #196)
Docker / Compose / Kubernetes were happily reporting calibre-web as healthy whenever the homepage returned 200 — even when Calibre's metadata.db was unreachable and OPDS, the book grid, and downloads were broken underneath. The HEALTHCHECK now targets the existing /health endpoint that runs SELECT 1 against metadata.db and returns 503 on failure, so orchestrators can route traffic away from a degraded node.
Repo hygiene (#194)
.cwa_migrations/ (a runtime marker directory created by cwa-init) is now ignored — no user-visible effect, just cleaner working trees for anyone who mounts /config at the repo root for local dev.
Credits
Thanks @droM4X for filing #190 and contributing #195, and for the right diagnosis behind #196 that became #197.