Navidrome Daily: Chasing Down Stale Data
Today's merges centered on fixing stale or incorrect data that clients silently trusted—cover art that wouldn't update, timestamps that sorted wrong, and lyric lines corrupted by unrecognized tags. The artwork fix, PR #5965, involved an extended engineering effort with multiple performance and correctness follow-ups after initial review.
Duration: PT2M14S
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-08-17T10:00:11Z
- Audio duration: PT2M14S
Transcript excerpt
This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.
Good evening, it's August 17th, 2026, and this is Navidrome Daily.
Tonight's theme: data that looked fine on the surface but was quietly wrong underneath, and the work it took to root that out.
The headline is PR #5965, from deluan, fixing artwork that failed to re-resolve when someone swapped a cover image on disk without touching any audio file. The scanner saw the folder change but never told the artwork queue, so clients kept serving old cover art until something else forced a refresh. What's notable…
Second theme: sorting and parsing correctness. PR #5867, from IgorPolyakov, fixes "Recently Added" ordering by keeping album creation timestamps in the database's native format instead of round-tripping them through Go and mismatching string formats. A quick follow-up commit also reordered a migration that would…
Third, PR #5966 fixes LRC lyric parsing so unrecognized tag lines like background-vocal markers don't get glued onto the wrong lyric line, which was corrupting timing and text.
What's next: watch for any regressions in artwork resolution timing or missed re-enqueues, given how many edge cases this touched. That's Navidrome Daily — see you tomorrow.