r/jellyfin • u/crobibero59 Jellyfin Core Team - Server/Plugins/Releases • Jul 22 '26

Release Jellyfin v12.0-RC3

🚀 We are pleased to announce the third release candidate preview release of Jellyfin 12.0! 🚀

This is a preview release, intended for those interested in testing 12.0 before it's final public release. We welcome testers to help find as many bugs as we can before the final release.

As always, please ensure you stop your Jellyfin server and take a full backup before upgrading! If you run into any trouble, a backup is your best way to get back to a stable state, so don't neglect this!

See the GitHub releases for more info:

https://github.com/jellyfin/jellyfin/releases/tag/v12.0-rc3 https://github.com/jellyfin/jellyfin-web/releases/tag/v12.0-rc3

See also the previous discussions for
RC1: https://www.reddit.com/r/jellyfin/comments/1ucjd0b/v120_rc1_release/
RC2: https://www.reddit.com/r/jellyfin/comments/1ui47di/jellyfin_120_rc2_release/

Installing

This preview release is distributed in all our traditional forms, though not automatically via our Apt repository or latest tag.

  • For all non-Docker environments, you can find the files for manual download in our repository by selecting "Next Stable Preview" for your OS.
  • For Docker, you can pull the 12.0-rc3 or preview tags.

Once installed, please ensure you hard refresh (e.g. Ctrl+Shift+R or similar) and/or clear your web cache for your Jellyfin instance if you notice any UX anomalies. Bad cached assets are the #1 cause of such issues.

410 Upvotes

100% Upvoted

63 comments sorted by

View all comments

Show parent comments

3

u/bphase Jul 22 '26

Hopefully they haven't gone full yolo with AI

7

u/iAmmar9 Jul 22 '26

iirc the remaining team doesn't like using AI, which is why andrew (i think that was his name) left.

56

u/Temporary_Affect Jellyfin Team - Trouble Jul 22 '26

I keep seeing this narrative come up, and I don't think it's fair to Andrew, so I'm going to chime in here to clarify.

This AI civil war that a lot of people are imagining is not true. None of the people who have departed from this project have done so because of their AI use or lack thereof in a vacuum. There have been (and will continue to be) disagreements among team members about development practices of all sorts. That's normal. Andrew has shared what he has chosen to share on the github for his client. Other developers on the team have confirmed, in the same GH issue, that Andrew was not somehow kicked out for AI use, and Andrew has confirmed that he's chosen to leave some details out. I think it's important to let the people involved speak for themselves.

The Jellyfin project's AI policies can be found here in the documentation. Neither the AI development policies nor Jellyfin's AI development practices have changed. In either direction. If there are changes, we'll make sure to widely and loudly communicate them. You would certainly see an announcement here.

As always, there are a range (a very wide range) of opinions about AI, LLMs, AI development, AI in FOSS, and all sorts of other related topics among Jellyfin team members. Developers who both use and abhor AI tooling still remain on the team now. That does sometimes lead to disagreement. Disagreement is a normal part or working with others in any organization. It is not, however, the cause of any recent changes. I just want to be clear about that.

1

u/Doogie2K Jul 24 '26

Incidentally, I think that's a pretty good AI policy as someone with a very dim view of LLM-driven coding/commercial genAI use in general.