If you can log into the site, it’s done.
If you try to access the site and you get a “startup log” page, it’s still ongoing (and it will show you there what it’s doing).
https://jellyfin.org/posts/jellyfin-release-10.11.0/#startup-ui-and-log-viewer

They are removing the hard to use old version that was inherited from the original Emby code.
For years now, the developers have been advocating the use of a reverse proxy to provide TLS.

I think the feel from the Devs is that there isn’t enough new functionality to justify the major version bump, this primarily being a reimplementation of existing features.

BUT, I agree with you, it should definitely be V11 under the semantic versioning scheme.
Whilst there is a migration path here, the database changes under the hood alone are likely to break backwards compatibility with all plugins (with in-house plugins being upgraded in sync).
Such breakage is kind of the defining characteristic of a MAJOR version.

This is not a remote code exploit that makes you vulnerable simply because 7zip is installed, which is the implication of the headline.
So this is a linkbait headline, divorced from the reality of the situation.
Which is the bit I take issue with.

The article itself describes not only the actual problem, but the broader problem of this being a known fixed problem which won’t be automatically addressed for most windows users.

Side note, winget is not bad as far as centralised package management goes for windows, and why I’m personally not at risk for this already long addressed 7zip issue.

“expose systems to remote attackers”.

This is some terrible link bait and Tom’s Hardware should be ashamed.