From ae984c15393851af291063a1bd6b1069f1e9f34b Mon Sep 17 00:00:00 2001
From: bartzbeielstein <32470350+bartzbeielstein@users.noreply.github.com>
Date: Tue, 2 Jun 2026 19:03:11 +0200
Subject: [PATCH] ci: relock uv.lock during release prepare and commit it

Prevents the lockfile's own-package version from lagging behind the
pyproject version semantic-release bumps (the drift PR #8 cleaned up by
hand). Add `uv lock` to the prepare phase between the version `sed` and
the build, and include uv.lock in the @semantic-release/git assets so
each release commits the aligned lockfile.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
---
 .releaserc.json | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/.releaserc.json b/.releaserc.json
index 4e60486..c51e0c9 100644
--- a/.releaserc.json
+++ b/.releaserc.json
@@ -138,6 +138,12 @@
         "prepareCmd": "sed -i 's/^version = .*/version = \"${nextRelease.version}\"/' pyproject.toml"
       }
     ],
+    [
+      "@semantic-release/exec",
+      {
+        "prepareCmd": "uv lock"
+      }
+    ],
     [
       "@semantic-release/exec",
       {
@@ -162,7 +168,8 @@
       {
         "assets": [
           "CHANGELOG.md",
-          "pyproject.toml"
+          "pyproject.toml",
+          "uv.lock"
         ],
         "message": "chore(release): ${nextRelease.version} [skip ci]\n\n${nextRelease.notes}"
       }