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...

cross-posted from: https://aussie.zone/post/36389875

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

___

  • @samc@feddit.ukEnglish
    11•5 hours ago

    I dont get why they didn’t just call that update 11.0? Or use that for this update?

    I guess if you’re changing the semantics of your version numbers its also a good idea to introduce a deliberate discontinuity to mark the change?

    • @CHOPSTEEQ@lemmy.mlEnglish
      2•1 hour ago

      I was confused too, but I guess their logic is that 10.11.x is 11.x.x. They might have been more explicit about that.