- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
https://forum.jellyfin.org/t-new-jellyfin-server-web-release-10-9-6
#Jellyfin Server 10.9.6
General Changes
Fix fallback artist when taglib fails [PR #11989], by @gnattu
Do not stop validation if folder was removed [PR #11959], by @Shadowghost
Use only 1 write connection/DB [PR #11986], by @Bond-009
Set ProductionLocations instead of Tags [PR #11984], by @Shadowghost
#Jellyfin Web 10.9.6
General Changes
Remove IMDb references [PR #5668], by @thornbill
Fix uneven slider value [PR #5667], by @dmitrylyzo
OMG, I haven’t even got 10.9.5 installed yet.
If this is the pace of updates, I fear for client devs
If they use semantic versioning, incrementing the last number means it’s only a bugfix release, so the API shouldn’t change. But as they say in their funding post, 10.10.0 will include API changes.
The reason this release was so fast is because of a critical bug that was locking the database to read only.
OMG! This was driving me nuts yesterday and I thought it was because I had just rerun docker compose and couldn’t figure it out. I ran a full recursive permission change on the jellyfin directory and reran the Ansible playbook and thought I fixed it. Turns out it just updated 10.9.6 when I reran the playbook, lmao