feat: Overseerr to Jellyseerr migration

[gauthier-th]

Description

This PR includes the migration script to convert an Overseerr instance into a Jellyseerr one.
The database migration is included in the server/lib/overseerrMerge.ts file, and has been generated using TypeORM. This migration will always be run after the UpdateWebPush1745492372230 migration, so that Overseerr users migrating much later doesn't run a new Seerr migration before the Overseerr->Seerr migration.

It also includes some renames of Jellyseerr -> Seerr I wrote when creating the first version of the migration.

This is what have been used by beta-testers to migrate their Overseerr instance.

To-Dos

• Disclosed any use of AI (see our policy)
• Successful build pnpm build
• Translation keys pnpm i18n:extract
• Database migration (if required)

[fallenbagel]

Noticed some places where there were typos.

Also one thing I'm concerned with is, with this merge, the docs will reference images that are currently not out there yet. Maybe we should add a temporary thing until then? We could add tabs in the installation docs for jellyseerr and overseerr and seerr. We can remove the first two tabs once the merge is fully completed

Wdyt? @sct @gauthier-th

[M0NsTeRRR]

Also one thing I'm concerned with is, with this merge, the docs will reference images that are currently not out there yet

Yes that’s why I proposed releasing the 2.7.3 image (in seerr-team/seerr) on the same commit as Jellyseerr, so everything can be updated prior to the next (first) release without breaking anything for existing jellyseerr users.

[fallenbagel]

Also one thing I'm concerned with is, with this merge, the docs will reference images that are currently not out there yet

Yes that’s why I proposed releasing the 2.7.3 image (in seerr-team/seerr) on the same commit as Jellyseerr, so everything can be updated prior to the next (first) release without breaking anything for existing jellyseerr users.

2.7.3 won't work though as it wont have the overseerr migration

[gauthier-th]

Also one thing I'm concerned with is, with this merge, the docs will reference images that are currently not out there yet. Maybe we should add a temporary thing until then? We could add tabs in the installation docs for jellyseerr and overseerr and seerr. We can remove the first two tabs once the merge is fully completed

Would disabling the CI to publish the docs be a solution for now, until the merge is completed?

[fallenbagel]

Also one thing I'm concerned with is, with this merge, the docs will reference images that are currently not out there yet. Maybe we should add a temporary thing until then? We could add tabs in the installation docs for jellyseerr and overseerr and seerr. We can remove the first two tabs once the merge is fully completed

Would disabling the CI to publish the docs be a solution for now, until the merge is completed?

That would work too

[M0NsTeRRR]

2.7.3 won't work though as it wont have the overseerr migration

No issue for me this image isn’t meant to handle the migration. The 3.0.0 release could be the first to do so. Currently, there’s no information confirming that the Seerr image is compatible with Overseerr, except for the preview-seerr tag from Jellyseerr.

[fallenbagel]

2.7.3 won't work though as it wont have the overseerr migration

No issue for me this image isn’t meant to handle the migration. The 3.0.0 release could be the first to do so. Currently, there’s no information confirming that the Seerr image is compatible with Overseerr, except for the preview-seerr tag from Jellyseerr.

That reminds me @gauthier-th we should merge this pr as a "breaking change" commit with that added. This would allow semantic version bot to release next version as 3.0.0

[M0NsTeRRR]

2.7.3 won't work though as it wont have the overseerr migration

No issue for me this image isn’t meant to handle the migration. The 3.0.0 release could be the first to do so. Currently, there’s no information confirming that the Seerr image is compatible with Overseerr, except for the preview-seerr tag from Jellyseerr.

That reminds me @gauthier-th we should merge this pr as a "breaking change" commit with that added. This would allow semantic version bot to release next version as 3.0.0

@sudo-kraken and me gonna rework the release part. As we use convetionnal commit you just need to commit with a ! and the changelog (git-cliff used on the other repo, e.g mobile app) will handle it :)

[Copilot]

Pull Request Overview

This pull request implements the migration from Overseerr to Seerr (the unification of Overseerr and Jellyseerr), including database migration logic and extensive rebranding throughout the codebase.

• Implements database migration logic to convert Overseerr instances to Seerr
• Replaces "Jellyseerr" references with "Seerr" throughout documentation and configuration
• Updates default database names, log file paths, and application titles

Reviewed Changes

Copilot reviewed 54 out of 60 changed files in this pull request and generated 5 comments.

Show a summary per file

File	Description
server/lib/overseerrMerge.ts	Complete migration script for Overseerr to Seerr conversion
server/index.ts	Integrates migration check into application startup
server/logger.ts	Updates log file naming from jellyseerr to seerr
server/datasource.ts	Updates default PostgreSQL database name
docs/*	Comprehensive documentation updates from Jellyseerr to Seerr
compose.yaml	Updates service and database names

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[github-actions]

This pull request has merge conflicts. Please resolve the conflicts so the PR can be successfully reviewed and merged.

[github-actions]

This pull request has merge conflicts. Please resolve the conflicts so the PR can be successfully reviewed and merged.

[github-actions]

This pull request has merge conflicts. Please resolve the conflicts so the PR can be successfully reviewed and merged.

[github-actions]

This pull request has merge conflicts. Please resolve the conflicts so the PR can be successfully reviewed and merged.

[sudo-kraken]

LGTM

[sct]

LGTM!