Fixed (licensing): the license key field is always visible, so a new key can be activated even while the saved license still shows as active; a refused key no longer replaces the saved key and the page shows why; when the last check fails (for example a deleted or revoked license), the page and the log show a warning with the date until which the saved license keeps working; activation, manual checks and release are written to the log.
Self-Update changelog
Every published version, newest first. The builds of our Jellyfin plugins and their complete source code are public (GPL-3.0); the plugin needs a license to run. Subscriptions and trials always get the latest version, lifetime licenses get updates within their update window.
0.1.3
Latest- The "License: active" badge is readable on dark themes (it was black text on a dark background).
- Security: the update status is read from root's folder (/var/lib/medialab-update-state), which the server user cannot change; with older updaters the old location is still read.
- Licensing security: exported logs no longer contain sensitive data, unencrypted license-server replies are refused, a plugin update or rollback is installed only with a valid medialab signature.
- Privacy: the payment QR code on the License page is now generated locally, in the page; the payment link is no longer sent to a third-party QR service (api.qrserver.com).
- First release: update and roll back medialab Server from the web UI (check, update to the latest or a chosen version, roll back to the previous version), with progress tracked across the server restart.
- Environment detection: medialab Server with the updater, medialab Server without the updater, official Jellyfin (with migration instructions).
- Daily task "Check for medialab Server updates" and optional automatic update (off by default) at a chosen hour.
- medialab.works licensing (product
jf-selfupdate): update and rollback require a license; checking does not.