Jellyfin 10.11.0 RC6 (github.com)
from Mountaineer@aussie.zone to jellyfin@lemmy.ml on 25 Sep 02:11
https://aussie.zone/post/25054481

Jellyfin, the open source media server, has released their 6th RC for version 10.11.0.

This is a preview release, intended for those interested in testing 10.11.0 before it’s final public release.

If you intend to test this, BE SURE you stop your Jellyfin server and take a full backup before upgrading!

WIP release notes here for now: https://notes.jellyfin.org/v10.11.0_features

See the GitHub link for more details and a full list of changes.

#jellyfin

threaded - newest

aeternum@lemmy.blahaj.zone on 25 Sep 04:43 next collapse

nice. Looks like they’ve made a number of significant changes. Always good to see.

notfromhere@lemmy.ml on 25 Sep 05:00 next collapse

I hope the EFCore migration will make it easier to eventually support external databases like Postgres

mushroomman_toad@lemmy.dbzer0.com on 25 Sep 07:48 collapse

There’s a PR already!

domi@lemmy.secnd.me on 25 Sep 11:39 collapse

Do you have a link for that PR?

Mountaineer@aussie.zone on 25 Sep 22:37 collapse

Looks like this is it: github.com/jellyfin/jellyfin/pull/13451 Also looks like the intention is to stabilise the new data layer before adding extra backends to avoid rework.

domi@lemmy.secnd.me on 26 Sep 08:24 collapse

Thanks, Github thinking it is merged explains why I was not able to find it.

Appoxo@lemmy.dbzer0.com on 25 Sep 05:23 next collapse

Looking forward to the release :)

stefenauris@pawb.social on 25 Sep 05:26 next collapse

I feel like something with such a major backend change that will affect compatibility deserves a higher version number. I’m going to tweak my docker compose file to ensure I dictate when this big database update happens

mushroomman_toad@lemmy.dbzer0.com on 25 Sep 07:47 next collapse

Yeah, there’s going to be a long, uninterruptable database migration at the next startup and they recommend taking backups before. My renovate is fully disabled for Jellyfin right now.

ShortN0te@lemmy.ml on 25 Sep 21:11 collapse

Be aware,

Jellyfin uses semantic versioning. All releases will have versions in the X.Y.Z format, starting from 10.0.0. Note however that the 10.Y.Z release chain represents the “cleanup” of the codebase, so it should be accepted that 10.Y.Z breaks all compatibility, at some point, with previous Emby-compatible interfaces, and may also break compatibility with previous 10.Y releases if required for later cleanup work

timeslip1974@lemmy.world on 25 Sep 05:50 next collapse

While a lot of backend changes,nothing from a user perspective wants to me jump on board…no new features and your extensions will break…I think I’ll wait lol

mushroomman_toad@lemmy.dbzer0.com on 25 Sep 07:48 collapse

There should be much better performance for browsing the library

imsufferableninja@sh.itjust.works on 25 Sep 13:16 next collapse

According to the release notes, the DB migration could take “up to several days” depending on library size. Oof.

Chewy7324@discuss.tchncs.de on 26 Sep 00:29 next collapse

Hopefully no one has their DB on an HDD…

AtariDump@lemmy.world on 26 Sep 00:53 next collapse

Or a Pi

[deleted] on 26 Sep 16:32 collapse

.

crazyminner@lemmy.ml on 06 Oct 09:13 collapse

Couldn’t I just rebuild the database completely? Start from scratch and have it just remake all the metadata?

imsufferableninja@sh.itjust.works on 06 Oct 10:25 collapse

Well you would lose the watched status for all your media, as well as any custom settings and whatnot.

My plan, when the time comes to upgrade, is to copy the DB and bring up an isolated container using the copy, let the upgrade proceed in the background, then swap to the new container when the upgrade is done. That way there’s minimal downtime and no data loss.

firepenny@lemmy.world on 25 Sep 14:21 next collapse

This is a great update. All said, this will break my system as i have a lot of configurations.

faercol@lemmy.blahaj.zone on 25 Sep 15:01 collapse

Yeah, I’m using the OIDC plugin, so I’ll need to wait as well

HereIAm@lemmy.world on 26 Sep 09:48 collapse

So when a full backup is recommended, does that include media files, or is it just the cache(?) and jellyfin database?

Mountaineer@aussie.zone on 26 Sep 10:28 collapse

Backup of the jellyfin cache, Configs and database.
Your media should be outside of all that. Exactly where those things are depends on your exact install method (native/docker/Linux/windows). jellyfin.org/docs/general/…/backup-and-restore/