chore: document manifest version sync (#67)

Author: Teagan42

AGENTS.md

@@ -51,6 +51,8 @@ The project should handle natural-language searches and recommendations such as:
 
 ## Versioning
 - Always bump the version in `pyproject.toml` for any change.
+- Mirror the version change in `docker/pyproject.deps.toml` so the Docker
+  dependency manifest stays consistent with the root project file.
 - Update `uv.lock` after version or dependency changes by running `uv lock`.
 
 ## Checks

README.md

@@ -80,11 +80,13 @@ running in a loop.
 ### Dependency Layer Workflow
 
 Docker builds now install dependencies using `docker/pyproject.deps.toml`, a
-manifest that mirrors the application's runtime requirements without the
-`[project]` version field. The `Dockerfile` copies that manifest and `uv.lock`
-first, runs `uv sync --no-dev --frozen --manifest-path pyproject.deps.toml`,
-and only then copies the rest of the source tree. This keeps the heavy
-dependency layer cached even when the application version changes.
+manifest that mirrors the application's runtime requirements. Keep the
+`[project]` metadata—including the `version`—identical to the root
+`pyproject.toml` so `uv sync` can reuse the shared `uv.lock` without
+validation errors. The `Dockerfile` copies that manifest and `uv.lock` first,
+runs `uv sync --no-dev --frozen --manifest-path pyproject.deps.toml`, and only
+then copies the rest of the source tree. This keeps the heavy dependency layer
+cached even when the application version changes.
 
 When cutting a release:
 

docker/pyproject.deps.toml

@@ -1,6 +1,6 @@
 [project]
 name = "mcp-plex"
-version = "0.26.33"
+version = "0.26.34"
 requires-python = ">=3.11,<3.13"
 dependencies = [
   "fastmcp>=2.11.2",

pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "mcp-plex"
-version = "0.26.33"
+version = "0.26.34"
 
 description = "Plex-Oriented Model Context Protocol Server"
 requires-python = ">=3.11,<3.13"