This hotfix release fixes Jellyfin 12 account linking and Seerr request ownership for Jellyfin/Emby recommendations, together with authentication reliability improvements and frontend dependency updates.
🔑 Jellyfin 12 Account Linking
- Fixed account linking by sending the modern
Authorization: MediaBrowser ...header - Retained the legacy authentication header for compatibility with Emby and older Jellyfin servers
- Jellyfin 12 no longer requires enabling legacy authorization to link an account
- Updated installation documentation and added regression coverage
Addresses #505.
👤 Correct Seerr Request Ownership
- Fixed Jellyfin/Emby recommendation jobs using the job owner's Seerr account instead of the user whose watch history is being processed
- Mapped Seer user (fallback to technical) now resolves the recommendation user's linked Seerr account
- Requests for mapped users use API-key authentication, supporting Jellyfin-authenticated Seerr accounts without a local password
- Unmatched users continue falling back to the configured technical identity
- Added paginated user lookup, UUID normalization, and lookup caching within each job run
Addresses #517.
🛡️ Seerr Authentication Reliability
- Requests with an explicit Seerr user ID now preserve that identity during queue delivery
- API-key requests no longer attempt local login when retrying HTTP 403 or 404 responses
- Expanded regression coverage for user mapping, fallback behavior, authentication retries, and queued requests
🧰 Maintenance & Dependencies
- Updated Swagger UI, Vite, Node.js type definitions, ESLint, eslint-plugin-vue, and globals
- Refreshed the frontend dependency lockfile
Dependency updates included in #514.