Jellyfin Server 12.2 arrived on October 5, the second maintenance release in the 12.x line, and the announcement keeps its promise modest: several bug fixes to improve your experience, with the standing advice to take a full backup before upgrading. The changelog runs to 51 entries, and the interesting ones cluster in playback, the library, and one refusal.
The fixes that matter
Dolby Vision profile 8 output now uses the hvc1 tag, the compatibility spelling that helps more players agree to play it. The bundled ATL library moves to 7.18.0, which fixes hangs triggered by malformed FLAC files, the kind of bad file that used to take a library scan hostage. EPUB metadata and covers load correctly on Windows now. The image and metadata side gets quieter correctness: local image dates compare with a one-second tolerance, changed ratings propagate only to children that follow them, and display preferences for an item are written in a single transaction. Several indexes go partial so that extras lookups keep using them, orphaned item values are cleaned up after deletions, and an off-by-one in the optimistic locking retry backoff is corrected. A second good guard sits in the same list: an unresolvable library is never treated as grounds for deletion, and the trickplay generator checks that the media directory is writable before starting. Graphical subtitles are served as raw files with range support now, bit-depth reduction stops wrecking low-bitrate video quality, and a segment cleaner bug that deleted chunks ahead of playback during MKV remuxing is fixed, which is the kind of thing that arrives just in time.
The refusal
The entry to file under good taste: a server in setup whose database is missing or empty now refuses to start rather than serving something strange. Failing loudly before a single client connects beats an empty-looking library discovered at eleven at night, and it is the kind of guard that only appears after someone has been burned.
My read
This is the release that pays off the rough edges of the 12.x transition: nothing here needs a configuration review, and nothing here is the kind of change that surprises you at the worst moment, the database guard excepted, which surprises you early by design. If you run the 12.x line, install it after a backup and move on with your weekend. If you have been holding on 11 until the dust settled, entries like this are what settled dust looks like. The habit the notes keep recommending is worth keeping: back up first, even for a point release, because the one bug that bites you is always the one nobody hit in testing. Fifty-one entries at this quality is what a healthy maintenance cadence looks like.
Source: the v12.2 release.