Mixarr v3.0.1 — TIDAL, AI, profile and shutdown fixes
Released November 17, 2026. Available for AMD64 and ARM64.
Mixarr v3.0.1 is a patch release with four community fixes. TIDAL subscriptions and search work again, the AI providers can use current Claude models, you can edit your own profile and password, and the unified container now stops cleanly. There are no database migrations or API breaking changes.
Every fix in this release was contributed by @kris-anderson. Thank you! Thanks also to @mdlopresti for the detailed TIDAL report.
See the website · Install Mixarr · Upgrade your installation
Fixes
TIDAL works with TIDAL's current API (#81, #98)
TIDAL removed the /userCollections/… and /userRecommendations/… endpoints on September 14, 2026. It also changed how search and playlist items work. Before this release, every TIDAL subscription and TIDAL as a search source failed with a 404 or 400.
- Favorite tracks, albums and artists, your playlists, playlist tracks, search, and similar artists now use TIDAL's current v2 endpoints, with cursor paging.
- Search results keep TIDAL's relevance order. Catalog requests use your account's country, or
USif it isn't set. - Videos in a playlist are skipped.
- Mix subscriptions are no longer available. TIDAL's public API has no replacement for discovery mixes, My Mixes or new-arrival mixes. The
tidal_discovery,tidal_mixandtidal_new_arrivalssubscription types now fail with a clear message instead of a 404. You can delete or pause them.
AI recommendations use a current Claude model (#94, #97)
- The Anthropic (Claude) provider now uses
claude-haiku-5-5. It usedclaude-3-haiku-20240307before, which Anthropic retired on April 19, 2026. - The OpenAI-compatible provider no longer sends
temperature: 0.7. That means current Claude models now work through Anthropic's OpenAI-compatible endpoint (https://api.anthropic.com/v1/). They used to reject the request with a 400. Other providers use their default temperature. - AI Recommendations with source Last.fm now seeds from your own top artists (
user.gettopartistsfor the connection's username and the subscription's period,overallby default). Before, it used Last.fm's global chart. A Last.fm connection without a username now gets the same "missing username" error as the other Last.fm subscriptions.
Edit your own profile and password (#95, #96)
Edit Profile → Save Changes and Change Password on the profile page used to fail with a 404. The API never registered the routes they call.
GETandPUT /api/auth/profileread and update the signed-in user's display name and email. No other fields can be changed. An email already used by another account is rejected.- SSO sign-in matches accounts by email. An account without a local password therefore can't change or clear its own email, because that would lock it out. An administrator can still change it from the Users page.
POST /api/auth/passwordchecks your current password, requires a new password of at least 8 characters, and is rate limited like sign-in. SSO-only accounts have no local password to change.- The profile dialog now shows your current email. Before, saving a display-name change sent an empty email, which would have erased it. That matters because SSO sign-in matches accounts by email.
The unified container stops cleanly (#99, #100)
Before this release, docker stop on the unified image always waited for the full stop timeout. Docker then killed everything, the bundled MariaDB included, and the container exited with code 137.
- supervisord now runs as PID 1, so it receives the
SIGTERMfromdocker stop. It stops the programs in reverse priority order: web and Caddy, then the API, then MariaDB and Redis. - MariaDB now receives the stop signal and shuts down normally. supervisord gives it up to 30 seconds to finish before forcing it.
- In the contributor's test, a stop that took 30.2 s and exited with code 137 now takes about 2 s and exits with code 0. MariaDB logs
Normal shutdown.
Docker's default stop timeout is 10 seconds. If you have a large database, you can raise it so MariaDB has time to flush, for example stop_grace_period: 60s in Compose or docker stop -t 60. The slim image already stopped cleanly and is unchanged.
Available images
Both variants are published for linux/amd64 and linux/arm64:
| Variant | Versioned image | Stable alias | Includes |
|---|---|---|---|
| Unified | ghcr.io/aquantumofdonuts/mixarr:v3.0.1
| :latest
| API, web, MariaDB, Redis, Caddy |
| Slim | ghcr.io/aquantumofdonuts/mixarr:v3.0.1-slim
| :slim
| API and web; uses external database and Redis |
Use the versioned tag to pin this release. The stable aliases can advance to future releases.
Upgrading
v3.0.1 has no schema changes. It upgrades in place from v3.0.0, and from released v2.x installations through the same checked migrations as v3.0.0.
As always, back up the database and persistent data first. Keep the same volumes, connection configuration, and SESSION_SECRET. For an existing Compose service named mixarr, change its image tag to v3.0.1 (or v3.0.1-slim), then run:
docker compose pull mixarr
docker compose up -d --no-deps mixarr
docker compose logs --tail=100 mixarrDocker Run and Unraid users should keep their saved environment and data mappings when updating the container. See the upgrade guide for details. Rolling back to v3.0.0 needs no data changes, but the pre-upgrade backup remains the recovery path.
Verification and limits
- The release went through the standard checks: lint and type checks, API and web tests, builds, release migration safety, upgrade rehearsals of both image variants, browser smoke tests, and CodeQL.
- The contributors checked the TIDAL and AI changes against the live provider APIs on November 1, 2026. Automated tests use mocked provider responses.
- TIDAL search returns the results on TIDAL's first result page (about 20 per type). Requests for more, such as the default 25-artist search, can return fewer.
- TIDAL access tokens are still refreshed in memory and not saved. This works as long as TIDAL doesn't rotate the refresh token, and a follow-up fix is planned. Jellyfin #87 and the other findings in docs/ISSUES.md remain open.