

Basically, yes. Forces plugins not to use potentially database-engine-specific SQL so that server admins don’t have to select their DB based on plugins for jellyfin being compatible.
Basically, yes. Forces plugins not to use potentially database-engine-specific SQL so that server admins don’t have to select their DB based on plugins for jellyfin being compatible.
I kinda agree here. https://jellyfin.org/docs/general/contributing/release-procedure/
Claims to follow semantic versioning, explicitly mentioning changes to plugin APIs as reasoning for a new major version.
That’s a spring hinge - I would not attempt to disassemble it. For this one, I’d use a light oil, like 3 in one oil or sewing machine oil and just do my best to get it into the hinge, either through the upper hole with the bar coming out of it, or allowing it to penetrate down the seam in the center of the top. You’ll probably need to work the door back and forth a bunch to get the oil where it needs to go.
“Breaks all compatibility [with emby]” was my interpretation of that. Not a huge deal either way but I’d definitely have been calling it 11 with this DB rework myself