Upgrade Path

Jellyfin 10.2.0 → 10.3.0

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

Version by version, oldest first

10.2.1 – 10.2.2: no action items (2 versions)

10.3.0 2019-04-19

Note

Release Notes

  • This release makes non-backwards-compatible changes to the users.db database (#870). Ensure you take a backup of this database (with Jellyfin stopped) before upgrading if you wish to revert back to an earlier release.
  • This release requires Windows users move the data directory from %APPDATA%\jellyfin to %LOCALAPPDATA%\jellyfin (#851). This is automatic with install-jellyfin.ps1. Based on RC testing this shouldn't cause any long-term problems.
  • The 3rd-party API no longer accepts pre-hashed passwords for authentication; the clients MUST send a plaintext password, and this MUST be encrypted via HTTPS to avoid password leakage. Administrators who do not use HTTPS already (either in-app or via reverse proxy) are strongly encouraged to do so.
  • Plugins installed with Jellyfin 10.2.Z might not upgrade properly due to a bug in the plugin management system that has now been corrected. If you encounter errors while upgrading a plugin, the easiest solution is to remove the plugin first, then re-add it. To preserve configuration as well, delete the plugin directory on the filesystem (e.g. in Debuntu/Fedora under /var/lib/jellyfin/plugins) the reinstall the newer version.
  • Users of Yatse should remove then re-add their Jellyfin server as the new Jellyfin type or authentication may fail.
  • OpenSubtitles support has been moved to a plugin.

Full release notes for 10.3.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.