Navidrome Daily: Fixing Stale Data on the Metadata and Rating Front
Today's changes tackle two sides of the same problem — making sure the UI reflects real, current state instead of stale or misidentified data, through a shared metadata refresh hook and a fix for duplicate track rendering in smart playlists.
Duration: PT2M5S
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-03T10:01:19Z
- Audio duration: PT2M5S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
It's September 3rd, and this is Navidrome Daily.
Today's work centers on one theme: keeping what you see on screen honest and in sync with what's actually in the library.
First, refreshing metadata. PR 6078, from Deluan, brings the "Refresh Metadata" action out of the context menu and onto the Album and Artist detail pages themselves. Previously, if you were already looking at an album or artist, you had no direct way to trigger a refresh — you'd have to back out to the list view.…
Second, and more critical: PR 6009 from polybjorn, tied to issue 6008, fixes a real correctness bug. When you rate or love a track, the app was refetching that row by its playlist position — but that position isn't a stable identity. In a smart playlist filtered by rating or love status, saving the annotation can…
Taken together: one change consolidates logic to prevent future drift, the other closes a data-integrity gap. Both are UI-layer fixes aimed at trustworthy state.
What's next: if you're touching hooks that patch rows by ID in dynamic or filtered lists, treat that position-as-identity assumption as suspect going forward.