Update overseerr to develop branch to fix issue with Plex watchlist sync

[joshdev8]

Summary by CodeRabbit

• Chores
  • Updated Overseerr service to use the “develop” container channel, enabling access to newer builds sooner.
  • Users may notice earlier availability of features and fixes, with a higher chance of instability compared to the stable channel.
  • The container will be recreated on the next deploy, which may cause brief downtime; existing data and settings should remain intact.
  • No user action required, though monitoring after deployment is recommended.

[coderabbitai]

Walkthrough

The docker-compose configuration for the Overseerr service was updated to use the image tag lscr.io/linuxserver/overseerr:develop instead of lscr.io/linuxserver/overseerr:latest. No other services or fields in docker-compose.yml were changed.

Changes

Cohort / File(s)	Summary
Compose Service Image Update docker-compose.yml	Change Overseerr service image from lscr.io/linuxserver/overseerr:latest to lscr.io/linuxserver/overseerr:develop. No other edits.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I twitch my whiskers at the quay,
A tag hops lanes from latest to dev today.
Compose hums softly, no storms to weather—
Just one neat image, light as a feather.
Carrot-shaped clouds, CI skies clear—
Ship it, ship it—Overseerr! 🍃🐇

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check	✅ Passed	The title succinctly and accurately describes the primary change—switching Overseerr to the develop image to address the Plex watchlist sync issue—and is a clear, single-sentence summary directly tied to the docker-compose.yml modification in the changeset.
Docstring Coverage	✅ Passed	No functions found in the changes. Docstring coverage check skipped.

✨ Finishing touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch overseerr-watchlist-sync-fix

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

• Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
• Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

docker-compose.yml (1)

248-248: Config volume path likely typo: overseer vs overseerr.

This will mount a different directory than intended, causing Overseerr to lose state or re‑initialize on each run.

Apply:

-      - ${USERDIR}/docker/overseer/config:/config
+      - ${USERDIR}/docker/overseerr/config:/config

🧹 Nitpick comments (1)

docker-compose.yml (1)

247-251: Optional: add a simple healthcheck for safer restarts and dependency ordering.

Helps Compose and tooling detect when Overseerr is actually ready.

     ports:
       - "5055:5055"
     restart: unless-stopped
+    healthcheck:
+      test: ["CMD-SHELL", "wget -qO- http://localhost:5055 > /dev/null || exit 1"]
+      interval: 30s
+      timeout: 5s
+      retries: 5

If Overseerr exposes a better status endpoint in your build, we can tighten this probe.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ba8e326 and 5735984.

📒 Files selected for processing (1)

• docker-compose.yml (1 hunks)

🔇 Additional comments (1)

docker-compose.yml (1)

242-255: Switch to develop tag: acceptable for the hotfix, but mitigate rollout risk.

Given the PR goal (fix Plex watchlist sync), moving Overseerr to lscr.io/linuxserver/overseerr:develop is reasonable. However, develop can introduce breaking changes and you have Watchtower auto‑updating nightly, which may pull untested builds.

Recommend one of:

• Pin the current digest to freeze the exact build, and bump intentionally later.
• Or exclude this one service from Watchtower until the fix lands in stable.

Example (choose one approach):

-    image: lscr.io/linuxserver/overseerr:develop
+    image: lscr.io/linuxserver/overseerr:develop@sha256:<digest_here>

or

   overseerr:
     image: lscr.io/linuxserver/overseerr:develop
+    labels:
+      - "com.centurylinklabs.watchtower.enable=false"

If you want, I can fetch the current image digest and propose an exact pin. Also, please confirm that this develop build indeed contains the Plex watchlist sync fix you need.