Is Navidrome v0.63.2 safe to update?

Yes, with care. No explicit breaking changes, but the notes mention migrations, deprecations or a new release line. Back up first.

⚠️ What breaks

Nothing explicitly breaking is flagged, but the notes mention migrations, deprecations or larger changes. Most setups upgrade fine. Back up first and update when you have time to check.

From the release notes

• be10f89c117925fabf10394b8d2962a370108b97: ci: don't skip release jobs after the DB migration check on tag pushes (#5760) (@deluan)
• 4381366e663b4647cfec1eb5597c39c3c42e9d7a: ci: validate DB migration order on pull requests (#5750) (@deluan)

Read the full official release notes →

✅ What to do first

1. Read the official release notes (linked in “What breaks”).
2. Back up config and data (snapshot the VM/volume if you can).
3. Note the version you are on now, so you can roll back.
4. Update, then check logs and core functions before walking away.

↩️ How to roll back to v0.63.1

Docker: snapshot/back up the data volumes first, then if needed change the tag back, e.g. image: deluan/navidrome:v0.63.1, and run docker compose up -d. Tag format varies by image (some drop the “v”), so check the registry’s tag list.