Skip to content

v0.61.54

Choose a tag to compare

View all tags
@github-actions github-actions released this 10 Jul 11:49
· 833 commits to main since this release
v0.61.54
74ee57a
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

WPMgr v0.61.54

Fixed

  • Media-encoder could silently stop all scheduled fleet jobs (GH #205). On self-hosted installs where the media-encoder ran using the API's default database schema (an unset or public WPMGR_RIVER_MEDIA_SCHEMA), the encoder could win the background-job leader election for the shared schema and stop the API from enqueuing every scheduled job, including backups, uptime checks, and cleanups, with no error anywhere. Background-job leader election is per-schema, so the fix is schema isolation:
    • The media-encoder now refuses to start on a default/public schema instead of risking the takeover.
    • A dedicated schema (media_encoder) is now the built-in default, so fresh and existing installs are safe with no configuration change. The schema self-heals on boot (created and migrated automatically).
    • The API logs a clear warning if it is ever configured to share its schema with a media-encoder.
    • Any media or screenshot jobs left behind in the shared schema from before this fix are moved to the dedicated schema and cleaned up on the encoder's next start.

Self-hosters on the bundled Compose stack are unaffected on upgrade: both the Compose files and the binary default supply media_encoder. If you run the API and media-encoder as separate custom deployments, set the same dedicated WPMGR_RIVER_MEDIA_SCHEMA value on both (never the API's default/public schema).

Images: ghcr.io/mosamlife/wpmgr/{api,web,media-encoder}:v0.61.54

Assets 3
Loading