Tindarr v1.1.0

Release Date: January 24, 2026

🆕 What's New in 1.1.0

Added user roles to allow forcematching of movies (SuperLike) by swiping up by elevated users, rely on matching or admin approval for non elevated
Added keyboard arrow controls for swiping (left/right) and curator force-match (up)
TMDB discover flow filters out Radarr library items and caches TMDB movie details
Added TMDB request rate limiting to stay within API limits
Added an Undo action between the like and nope buttons that animates the previous card sliding back into view
The client keeps an interaction history and calls a backend endpoint to remove the last interaction so the database state is rolled back (optimistic UI with server reconciliation)

Updated the Admin Console and SwipeDeck to better support tall, narrow (mobile) screens: cards scale on mobile and layouts stack responsively
The Plex verification bubble and other admin panels now adapt and stack vertically on mobile devices

Admin overview can check for updates against GitHub releases
Users tab: "Add all user movies" now force-matches and adds to Radarr
Admin Console logs POST /api/v1/plex/servers calls so you can verify payloads without opening dev tools

Global debug mode toggle (admin-only) now surfaces API payloads and responses on every page

Moved the Plex token from per-user storage to a global AppSettings entry and added an Admin Console tab to manage it
Added a Plex token verification endpoint that validates the token against Plex, returns user thumb, title, and email, and flags Plex Pass accounts
Removed server-side runtime image processing for Plex assets — the frontend now serves a bundled image instead

Plex server settings now use a dedicated table so EnabledLibraryIds and tokens persist across restarts
Fresh installs automatically create the Plex join table, eliminating the "libraries never save" issue

Pre-commit hook syncs version across backend, frontend, and installer metadata
Installer improvements: the backend supports an installer-time --migrate-db flag so EF Core migrations can be applied during installation (installer invokes the installed backend to run migrations)