TECH Signal 608 2 feeds carried it
Jellyfin 12.0 drops version 10 prefix, rewrites database on first boot, breaks old clients and plugins
↗
Jellyfin 12.0 is a major release that changes the version numbering scheme from 10.x to 12.x, rewrites the database schema on first boot, and removes support for legacy client endpoints and old third-party plugins.
Engineers upgrading to Jellyfin 12.0 must take a full backup before upgrading because the database migration is irreversible, and they must run a full library scan afterward. The version numbering change will break any scripts, clients, or monitoring tools that parse Jellyfin version strings.
Written by elseif from the cluster below · every claim links back to a sourceThe three things worth knowing
The database schema changes and actively rewrites data on first boot, making a backup the only way to roll back.
Third-party plugins built for 10.11 will not load on 12.0, and very old clients using legacy /emby/ or /mediabrowser/ endpoints will stop working.
The version numbering scheme drops the leading "10", changing from 10.12.0 to 12.0, which will affect anything that parses Jellyfin version strings.
THE CLUSTER