ReadAIrr changelog

What changed, what is stabilizing, and what comes next.

This page captures the current public baseline for ReadAIrr: a fork that is preserving the useful Readarr automation model while adding audiobook-specific matching, clearer deployment paths, and independent update infrastructure.

Public baseline and development reset

ReadAIrr now has a coherent public story: the app, site, docs, update service, and container image are being pulled under the ReadAIrr name while inherited Readarr compatibility names remain only where the app still depends on them.

  • ReadAIrr branding has been swept through visible app and website surfaces.
  • Old donation and upstream-community links have been removed from the app status surfaces.
  • The website now highlights current ReadAIrr direction instead of presenting only legacy Readarr feature copy.

Narrator and unmatched-file workflows

ReadAIrr is moving audiobook metadata into the matching workflow instead of treating it as a decoration after import.

  • A Narrators area now has room for missing-narrator review.
  • STT evidence can be considered beside metadata support and user confirmation.
  • Multi-part unmatched books are being grouped as one UI entry when folder names, title clues, and numbering indicate a single book.
  • For multi-part entries, STT is intended to run against the first file only, avoiding repetitive scans of every part.

Hosted metadata first, custom service optional

New installs default to the hosted Goodreads-compatible service, with a hosted Hardcover-compatible option and an escape hatch for users who already run a compatible metadata service.

  • Default metadata source: https://api.bookinfo.pro.
  • Alternative hosted option: https://hardcover.bookinfo.pro.
  • Custom rreading-glasses URLs remain supported, for example http://rreading-glasses:8788.
  • Metadata settings can be tested before saving so users can confirm the selected service is reachable.

Docker, Postgres, Unraid, and updates

Deployment work is being made explicit so public users can test the app without reverse-engineering the fork.

  • The maintained image is ghcr.io/readairr/app.
  • Public Docker tracks are dev, val, and prod.
  • The first-party Docker Compose path runs ReadAIrr plus a same-stack Postgres container.
  • The Unraid template exposes branch selection, Web UI URL formatting, and optional external Postgres connection settings.
  • Versioning is moving toward major-version clarity with development, validation, and production update streams.

Moving forward

The near-term focus is to keep tightening the fork-independent release path, publish clearer docs for public testing, and make narrator-aware import review feel natural enough that audiobook collections do not need a separate manual spreadsheet to stay clean.

Follow development on GitHub