- cross-posted to:
- selfhosted@lemmy.world
- opensource@lemmy.ml
- cross-posted to:
- selfhosted@lemmy.world
- opensource@lemmy.ml
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
You must log in or register to comment.
Looks like the Jellyfin Ignore plugin will not be compatible and it hasn’t been updated in two years.
Anyone know of a compatible alternative?My container updated to 12 overnight. I have jellyfin ignore installed and its still listed as active. Its version 0.5.0.0
For the couple months I’ve noticed Swiftfin has had a message in the settings screen saying I should upgrade to Jellyfin 12 or some features won’t work properly.
Jellyfin 12 wasn’t even released yet.
Awww, yeah!!! Who’s gonna upgrade first and let us know if anything breaks??
What a banger release! Super excited for the future. I know some folks were worried about the change in leadership, but this is super promising. Heres hoping runway is clear for Postgres at some point.
Why?
Why what? Why do I want Postgres? Because my database is on an iSCSI partition that is brittle.
Why? 😜
Your answer only opened more questions for me so I’m going to conclude this is above my head lol.
I’m happy to provide more details if you’re interested/have specific questions.
I’m running the Jellyfin app on my home kubernetes cluster – Kubernetes (k8s) boils down to a program scheduler with a lot of big features a lot of IT folks like. K8s runs the Jellyfin program as a “pod”, and it attaches remote storage to the pod. The storage is your videos/media, but also the Jellyfin database (as a sqlite file).
There are better, more reliable ways to provide a database to an app though. Jellyfin + the sqlite database is basically just a file and that file doesn’t exactly play nice when it is stored remotely. Instead, the app could use a software interface (API) that allows many kinds of databases – sqlite OR a dedicated database service (e.g. Postgres), and there are a lot of advantages to that.
no version 11?
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.
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.
