Kha-kis/arr-dashboard v3.0.0-alpha.1

v3.0.0-alpha.1 — Bucket A: the breaking-changes bundle

on GitHub

First 3.0 preview. All breaking changes land together (charter §3) so upgraders absorb the disruption once.

⚠️ Preview release — run it via the :next Docker tag (khak1s/arr-dashboard:next), which currently points at this snapshot and keeps rolling toward alpha.2. Pin by digest if you want to stay exactly here. :latest remains 2.21.0 and is untouched by this tag.

BREAKING — Tautulli removed (ADR-0007)

Plex statistics now come directly from session snapshots; Tracearr arrives later in the 3.0 cycle as the analytics successor.

The migration is automatic and consent-gated. On first boot, a blocking dialog discloses exactly what changes — your lingering Tautulli instances and any cleanup/auto-tag rules that referenced Tautulli watch data — and deletes Tautulli data only when you click through. Rules that depended on Tautulli are disabled, never deleted, with originals backed up to <config>/rules-pre-3.0/. Your watch history is not lost: it remains inside Tautulli itself, and Tracearr's importer reads it from there when it lands.

Rollback: the 2.21.0 image runs against the same database. Re-add your Tautulli instance manually and re-enable any disabled rules.

Changed

• Unified rule engine (ADR-0006) — library-cleanup, auto-tag, and notification rules all evaluate through one grammar-based engine. Behavior-preserving, proven by a 48-fixture differential parity suite against the legacy evaluators. Your stored rules are not rewritten — they convert in memory and only write the new format when edited.
• Rule writes now reject unknown/retired condition kinds with a clear error instead of silently accepting them.
• Route-manifest tiers reshuffled per ADR-0005; qui and Cross-Seed promoted experimental → stable.
• Internal: routes/plex/lib/ → lib/media-stats/, queue-cleaner dev scripts removed, inline Body: typings migrated to validateRequest.

Known issues

• Settings → Notifications → Rules can log a "Maximum update depth exceeded" warning on mount (pre-existing in 2.x, not a regression).

What's next

3.0-alpha.2..N land the Bucket B coherence sweeps progressively on :next; flagships (Operator Console + rule composer, Tracearr, Setup rewrite) follow in the betas. Full plan: 3.0 charter.

🤖 Generated with Claude Code