Upgrade Path

Jellyfin 10.5.0 → 10.6.0

6 versions, 1 with upstream notes, none marked as breaking by the vendor, 0 required stops

Version by version, oldest first

10.5.1 – 10.5.5: no action items (5 versions)

10.6.0 2020-07-19

Note

Release Notes

  • [ALL] Memory usage may be higher in 10.6.0 compared to previous versions. We have had several, but not many, reports of high memory usage in unstable 10.6.0 builds, most often caused by frequent library scanning. The current consensus is that this is due to the garbage collection in C# not being agressive enough. There are future plans to investigate and address this further in a general way, but the situation right now does not seem serious enough to block a stable release. If it does become evident that this is a major issue, a fix will be prioritized for a 10.6.1 release.
  • [ALL] This release introduces the first of several major database schema changes as we move to EF Core, specifically to the User and Activity databases. UPON UPGRADING YOUR INSTANCE TO 10.6.0, YOU WILL NOT BE ABLE TO DOWNGRADE TO 10.5.5 OR EARLIER WITHOUT RENAMING AND EDITING MUTIPLE FILES IN MUTIPLE PLACES. Make a backup of your instance before upgrading so downgrades can be a smooth and simple process.
  • [ALL] This release features a simultaneous release of jellyfin-ffmpeg v4.3.1. You should upgrade both at the same time for maximum compatibility, performance, and stabiity. However...
  • [Debian/Ubuntu amd64 .debs] The updated jellyfin-ffmpeg v4.3.1 was not built on the following older releases due to an build failure of an additional included amd64-only dependency. Users of these releases will continue to use jellyfin-ffmpeg v4.2.3. This should be fine unless you wish to use QSV, which was buggy in v4.2.3; if you do, we recommend upgrading to a newer operating system version for your Jellyfin instance or switching to Docker-based installs in order to take full advantage of jellyfin-ffmpeg v4.3.1.
  • Debian Stretch (9.x)
  • Ubuntu Xenial (16.04)
  • [Debian/Ubuntu Repository] ~The seamless apt upgrade seems to have been more troublesome than anticipated. If your upgrade fails, immediately run apt -f install with no other options and this should correct the situation. If not, try running apt install jellyfin-server instead.~ Fixed by package version 10.6.0-2 of jellyfin-server and jellyfin.

Full release notes for 10.6.0

Release notes from github.com/jellyfin/jellyfin/releases, and the official release blog, checked 17 hours ago. Only text the vendor marks as breaking, or puts in a warning/caution/important/stop/notice note, or a plain note, is shown (a note that only says when security advisories will be published is not); read the full notes for anything else. Jellyfin's release notes mark breaking changes only from 12.0 (“Breaking and behavior changes”). Sections titled Important Release Notes, Important Notes, Notes on Updating and the 10.4.1 Base URL change, and a Packaging section (12.0: platforms no longer built) are quoted as “Note”; so is the Release Notes section of x.y.0 releases. In patch releases, whose Release Notes list bug fixes, only paragraphs with a bold WARNING, STOP, NOTICE or NOTE marker are quoted. From the release blog (jellyfin.org/posts, 10.9.0 onward) the Breaking Changes sections are quoted as “Breaking”, and the TL; DR, Removal of …, Deprecation of …, Free Space Checks and Changes you may notice after upgrading sections as “Note”; four bullets of the 10.9.0 “The Big Changes” lists that remove or reset something (DLNA, PIN login, minimum FFmpeg, FFmpeg path) are quoted as “Note” too.