New Jellyfin Server/Web release: 10.9.6

[ReleaseBot]

We are pleased to announce the latest stable release of Jellyfin, version 10.9.6!

This minor release brings several bugfixes to improve your Jellyfin experience.

As always, please ensure you stop your Jellyfin server and take a full backup before upgrading!

You can find the full changelogs on the GitHub releases for the server repository and the web repository.

Release prepared with <3 by @joshuaboniface, the rest of the Jellyfin team, and contributors like you.

Happy watching!

[joshuaboniface]

For our Docker users, we now have additional tags you can use to more granularly pull the images! This applies both to Docker Hub and GHCR. Going forward, we'll be publishing tags like so:

latest, always tracks whatever the latest release is, including through major and minor version bumps
X (e.g. 10), tracks the latest in 10.y.z (which is our "major" version for the forseeable future) NEW
X.Y (e.g. 10.9), tracks the latest in 10.9.z minor, good for those who don't want to jump right to 10.10 later on but want the bugfix releases automatically NEW
X.Y.Z (e.g. 10.9.6), tracks the specific point release
X.Y.Z.YYYYMMDD-HHMMSS (e.g. 10.9.6.20240606-184155), tracks the specific packaging build, which in future might change for long-running stable releases to update dependencies and such, while still tracking the same Jellyfin code revision (i.e. vX.Y.Z tag)

[KodiUser1138]

LOL I didn't even update to 10.9.4 after recovering my 10.9.3 server and 10.9.5 was released and now 10.9.6. So do I tempt fate???

[rigrig]

That was pretty quick after 10.9.5, thanks!

The new docker tags are also neat.
Is it "safe" to e.g. run a cronjob to auto-update to the latest X(or X.Y) tag? I mean: would there be any chance of needing manual upgrade steps between say 10.12 and 10.13?

[joshuaboniface]

would there be any chance of needing manual upgrade steps between say 10.12 and 10.13?

Yes, that I would definitely avoid. "Minor" (really, I call them major, but our implementation of SemVer is weird) updates are the ones likely to introduce big changes or require administrator intervention, so for those, I wouldn't advise doing automatic upgrades without first reading the release notes. Minor versions *should* (usually) be safe to auto-upgrade, our database-issue-trying-to-fix spree in 10.9.z notwithstanding.

[PuppetSin]

Thanks for the quick turnaround, you guys rock!

[BoomBlooper]

Thanks so much! This release fixed two of the issues I was having!

[rigrig]

Minor versions *should* (usually) be safe to auto-upgrade, our database-issue-trying-to-fix spree in 10.9.z notwithstanding.

Thanks, pinning to 10.9 it is. (When there's a new release I tend to go "Ooh, shiny!" and update manually before reading the forum/issues anyway, I've got backups ;-)

[messiah1095]

Thanks for the quick update, fixed the issues I was having with 10.9.5

[Host-in-the-Shell]

Thanks for all the hard work and addressing any issues in such a speedy manner!