Release/v2.0.0 seerr migration

[jhomen368]

PR Type

Enhancement

---

Description

• Add Seerr support with dual environment variables (SEERR_/OVERSEERR_)

• Maintain 100% backward compatibility with deprecation warnings for legacy variables

• Update branding from Overseerr to Seerr throughout codebase

• Enhance health check endpoint with compatibility list

• Bump version to 2.0.0 with comprehensive migration guide

---

File Walkthrough

	Relevant files
Enhancement	index.ts Implement Seerr support with backward-compatible environment variables src/index.ts Rename validation function from validateOverseerrUrl to validateSeerrUrl Implement dual environment variable support with SEERR_* taking precedence over OVERSEERR_* Add deprecation warnings for OVERSEERR_* variables (removal planned for v3.0.0) Update error messages and server branding to use "Seerr" terminology Enhance health check endpoint to include compatibility list ['seerr', 'overseerr', 'jellyseerr'] Update startup logging messages to indicate support for both Seerr and Overseerr instances +41/-22
Configuration changes	version.ts Update version to 2.0.0                                                                    src/version.ts Bump version from 1.2.4 to 2.0.0 +1/-1      package.json Update package metadata for v2.0.0                                              package.json Bump version from 1.2.4 to 2.0.0 Update description to reference both Overseerr and Seerr Add "seerr" and "jellyseerr" keywords +4/-2
Documentation	CHANGELOG.md Add v2.0.0 release notes with migration guide                        CHANGELOG.md Add comprehensive v2.0.0 release notes documenting Seerr support Document dual environment variable support with precedence rules Include detailed migration guide for existing Overseerr users Clarify that all changes are backward compatible with no breaking changes Document deprecation timeline for OVERSEERR_* variables (removal in v3.0.0) +60/-0    CONTRIBUTING.md Update contributing guide for Seerr support                            CONTRIBUTING.md Update title and description to reference Seerr MCP Server Update prerequisites to accept both Seerr and Overseerr instances Update environment variable examples to use SEERR_* naming convention Update testing instructions to reference Seerr or Overseerr instances +6/-6      Dockerfile Update Dockerfile environment variable documentation          Dockerfile Update environment variable documentation to reference both SEERR_* and OVERSEERR_* (legacy) Add note indicating SEERR_* variables are preferred Clarify that OVERSEERR_* variables will show deprecation warnings +3/-2      README.md Update README with Seerr branding and migration guide        README.md Update title from "Overseerr MCP Server" to "Seerr MCP Server" Update version badge from 1.2.4 to 2.0.0 Revise description to emphasize Seerr as primary with Overseerr as legacy option Update prerequisites to reference Seerr or Overseerr instances Update Quick Start examples to use SEERR_* environment variables Add legacy Overseerr user section with backward compatibility note Update Docker examples to use SEERR_* variables and seerr-mcp container name Update troubleshooting section to reference Seerr/Overseerr Update acknowledgments to include Seerr as primary tool +38/-22

---

[qodo-code-review]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
⚪	🎫 No ticket provided Create ticket/issue
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
⚪	No custom compliance provided Follow the guide to enable custom compliance check.
Update

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[qodo-code-review]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
General	✅ Consolidate deprecation warnings for clarity Suggestion Impact: Replaced two separate deprecation warning blocks with consolidated logic using isUsingLegacyUrl/isUsingLegacyApiKey and a single warning message plus per-variable migration hints. code diff: // Log deprecation warning for Overseerr variables (non-intrusive) -if (process.env.OVERSEERR_URL && !process.env.SEERR_URL) { - console.error('[DEPRECATION WARNING] OVERSEERR_URL is deprecated. Please use SEERR_URL instead.'); - console.error('[DEPRECATION WARNING] Support for OVERSEERR_* variables will be removed in v3.0.0'); -} -if (process.env.OVERSEERR_API_KEY && !process.env.SEERR_API_KEY) { - console.error('[DEPRECATION WARNING] OVERSEERR_API_KEY is deprecated. Please use SEERR_API_KEY instead.'); - console.error('[DEPRECATION WARNING] Support for OVERSEERR_* variables will be removed in v3.0.0'); +const isUsingLegacyUrl = process.env.OVERSEERR_URL && !process.env.SEERR_URL; +const isUsingLegacyApiKey = process.env.OVERSEERR_API_KEY && !process.env.SEERR_API_KEY; + +if (isUsingLegacyUrl || isUsingLegacyApiKey) { + console.error('[DEPRECATION WARNING] Legacy OVERSEERR_* variables are in use. Support will be removed in v3.0.0.'); + if (isUsingLegacyUrl) { + console.error(' - Please migrate from OVERSEERR_URL to the preferred SEERR_URL.'); + } + if (isUsingLegacyApiKey) { + console.error(' - Please migrate from OVERSEERR_API_KEY to the preferred SEERR_API_KEY.'); + } } Consolidate the deprecation warnings for legacy OVERSEERR_* environment variables to prevent duplicate messages and improve log clarity. src/index.ts [151-159] // Log deprecation warning for Overseerr variables (non-intrusive) -if (process.env.OVERSEERR_URL && !process.env.SEERR_URL) { - console.error('[DEPRECATION WARNING] OVERSEERR_URL is deprecated. Please use SEERR_URL instead.'); - console.error('[DEPRECATION WARNING] Support for OVERSEERR_* variables will be removed in v3.0.0'); -} -if (process.env.OVERSEERR_API_KEY && !process.env.SEERR_API_KEY) { - console.error('[DEPRECATION WARNING] OVERSEERR_API_KEY is deprecated. Please use SEERR_API_KEY instead.'); - console.error('[DEPRECATION WARNING] Support for OVERSEERR_* variables will be removed in v3.0.0'); +const isUsingLegacyUrl = process.env.OVERSEERR_URL && !process.env.SEERR_URL; +const isUsingLegacyApiKey = process.env.OVERSEERR_API_KEY && !process.env.SEERR_API_KEY; + +if (isUsingLegacyUrl || isUsingLegacyApiKey) { + console.error('[DEPRECATION WARNING] Legacy OVERSEERR_* variables are in use. Support will be removed in v3.0.0.'); + if (isUsingLegacyUrl) { + console.error(' - Please migrate from OVERSEERR_URL to the preferred SEERR_URL.'); + } + if (isUsingLegacyApiKey) { + console.error(' - Please migrate from OVERSEERR_API_KEY to the preferred SEERR_API_KEY.'); + } } [Suggestion processed] Suggestion importance[1-10]: 6 __ Why: This suggestion correctly identifies that the deprecation warning can be logged multiple times and proposes a cleaner, consolidated logging approach that improves the user experience by reducing log noise.	Low
Update