Release 12.0 · jellyfin/jellyfin
github.com
🚀 Release notes for 12.0 Notes on Updating Before upgrading from an earlier version, a full backup of the data directory is strongly recommended, as this release includes database changes that prev...

Why jump from 10.11.11 directly to 12.0? -> Blog Post

You can find more details about and discuss this release on the official forums.

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

Direct upgrades from 10.10.7 and 10.11.x to 12.0 are supported; intermediate upgrades are not required. Users running releases older than 10.10.7 are strongly encouraged to upgrade to 10.10.7 before migrating to 12.0.

Installed repository plugins (anything not built-in) should also be removed before migrating. Plugins will likely need time to adapt to the new database changes, so re-adding them afterward is the safest approach for testing.

Official plugins compatible with Jellyfin are available through the stable plugin repository. If you have changed to the unstable plugin repository please change it back.

Go to Dashboard -> Plugins -> Manage Repositories
Update the Plugin Repository URL to: https://repo.jellyfin.org/files/plugin/manifest.json

After migrating please perform the following steps.

Perform a full library scan to restore alternative versions
Run the "Optimize database" scheduled task

___

    • Mountaineer@aussie.zoneOPEnglish
      13·
      19 hours ago

      From the blog post I have added to the original post:

      The most visible change in this release is the one in its name: we are dropping the major version “10” from our naming scheme. What would have been 10.12.0 is simply 12.0, and the server reports its version as 12.0.0. 10.11.x was the last release branch to use the old scheme.

    • curbstickle@anarchist.nexusEnglish
      10·
      19 hours ago

      Skipped to simplify versioning and avoid confusion.

      X.Y.Z - changing X only happened with breaking changes to the api. Y would then be big, big updates, but minor in terms of the API (and backwards compatible), and Z for bugfixes and minor updates.

      Now the major will be major changes, not just api-breaking ones.