fix(release): keep the Python lockfile version consistent (#12)

Author: sid-rl

.github/workflows/ci.yml

@@ -28,6 +28,9 @@ jobs:
         with:
           version: '0.10.2'
 
+      - name: Check lockfile before installing dependencies
+        run: uv lock --check
+
       - name: Install dependencies
         run: uv sync --all-extras --group docs
 

CONTRIBUTING.md

@@ -150,6 +150,18 @@ $ ./scripts/format
 
 ## Publishing and releases
 
+The checked-in `uv.lock` must match `pyproject.toml` before dependency installation.
+CI checks this with its pinned uv version (0.10.2). Refresh with that version of
+`uv lock`, without upgrading dependencies, when changing package metadata.
+
+Release Please updates the editable root package in `uv.lock` through its TOML
+extra-file updater. The name filter uses `name.value` because the pinned
+Release Please 17.3.0 parser represents TOML strings as tagged values. When upgrading
+the release action, verify a simulated version bump changes only the root package's
+version and that `uv lock --check` still succeeds; never target a positional package
+index or apply a version replacement to all dependencies.
+
+
 Changes made to this repository via the automated release PR pipeline should publish to PyPI automatically. If
 the changes aren't made through the automated pipeline, you may want to make releases manually.
 

release-please-config.json

@@ -61,6 +61,11 @@
   ],
   "release-type": "python",
   "extra-files": [
-    "src/runloop_api_client/_version.py"
+    "src/runloop_api_client/_version.py",
+    {
+      "type": "toml",
+      "path": "uv.lock",
+      "jsonpath": "$.package[?(@.name.value == \"runloop-api-client\")].version"
+    }
   ]
-}
+}