Switching from the third-party OIDC-capable jellyseerr fork to the
mainline successor project (Seerr - the combined Overseerr+Jellyseerr
team rebrand, v3.0.0 / Feb 2026 onward). Mainline now has native OIDC
support so the custom preview-OIDC build isn't needed.
- Image : docker.io/fallenbagel/jellyseerr:preview-OIDC
-> ghcr.io/seerr-team/seerr:v3.3.0 (Jun 2, 2026)
- Migration: automatic on first start per docs.seerr.dev/migration-guide;
existing sqlite db + settings.json in /app/config are
directly compatible. v3.1.x added CVE-2026-40175 fix +
auth-related security patches, so v3.3.0 is the right
floor anyway.
- Backup : ~/seerr-backups/seerr-config-20260606-153633.tar.gz on
dooplex (covers db.sqlite3 + settings.json + logs).
Rollback = revert image + restore tarball into the PVC.
Worth verifying after rollout:
- Pod becomes Ready (readiness probe path /api/v1/status -- should
still exist in seerr).
- Authentik OIDC sign-in still works. If the custom build used
different config keys than mainline seerr expects, OIDC may need
re-configuration in the seerr UI (Authentik side unchanged).
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
admin
d67ec2af65