Navidrome Daily: Jellyfin Compatibility Gets Serious
A single but substantial fix reshapes how Navidrome's Jellyfin API formats its responses, closing gaps that broke strict third-party clients. A smaller translation update rounds out the day's merges.
Duration: PT2M15S
Episode overview
This episode is a short developer briefing from Navidrome Daily.
It explains recent repository work in plain language.
- Show: Navidrome Daily
- Published: 2026-09-17T10:02:54Z
- Audio duration: PT2M15S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good day, and welcome to Navidrome Daily for September 17th, 2026.
Today's headline is really one story told across a merge and two follow-up commits: Navidrome's Jellyfin-compatible API wasn't speaking Jellyfin's dialect closely enough, and that broke real clients.
The trigger was issue 6147: a Jellyfin client called Manet would log in fine, then show an empty library. PR 6151, from Deluan, traces the cause to strict decoding — Manet's sync aborts entirely the moment it hits one missing field. And it turns out there were several: date formatting didn't match .NET's expected…
What's notable is the engineering discipline in the follow-up commits. Rather than patching each mapper separately, the code was refactored twice — first to share one helper for default empty fields, then to push all the "always present" fields to a single serialization point, nicknamed stamp-item in the commit log.…
The practical takeaway: this wasn't a one-off client accommodation. It was verified against an actual Jellyfin 10.10.7 server, and the fix targets protocol correctness, not Manet specifically. That should reduce future compatibility bug reports from other strict clients.
Separately, PR 6152 updated…