From cfd968aced71b6c7dffb7adcf59a64fa30f40374 Mon Sep 17 00:00:00 2001
From: Chris Farhood <chris@farhood.org>
Date: Mon, 20 Jul 2026 10:13:56 -0400
Subject: [PATCH] fix(release): sync uv.lock into the bump commit and tag

After cz bump changes the project version, regenerate uv.lock and amend it into
the bump commit (moving the tag) so every release tag stays consistent and
`uv sync --locked` works when the versioned image is built.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NGzHtDvJur9U7ysgRKRUTN
---
 .gitea/workflows/release.yaml | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/.gitea/workflows/release.yaml b/.gitea/workflows/release.yaml
index 57ba76b..7325786 100644
--- a/.gitea/workflows/release.yaml
+++ b/.gitea/workflows/release.yaml
@@ -59,6 +59,15 @@ jobs:
           fi
           if uvx --from commitizen cz bump $args; then
             after=$(uvx --from commitizen cz version --project)
+            # cz bump updates pyproject's version but not uv.lock's own-package
+            # entry, which would leave `uv sync --locked` failing at the release
+            # tag. Refresh the lock and fold it into the bump commit + tag.
+            uv lock
+            if ! git diff --quiet uv.lock; then
+              git add uv.lock
+              git commit --amend --no-edit
+              git tag -f "v$after"
+            fi
             echo "version=$after" >> "$GITHUB_OUTPUT"
             echo "do_release=true" >> "$GITHUB_OUTPUT"
             echo "Bumped $before -> $after"