From 66b85c8b62e5fba27de1ed662bbea1d518ee275b Mon Sep 17 00:00:00 2001 From: irfanuddinahmad Date: Thu, 27 Aug 2026 17:26:07 +0500 Subject: [PATCH] fix: build with uv instead of pip in the uv-run PSR step #435's uv-based workaround got past the GitPython crash (confirmed: correctly computed "The next version is: 4.1.1!") but hit a new failure at the build step: PSR's build_command shelled out to 'python -m pip install --upgrade build', and uv's ephemeral venvs deliberately don't bundle pip the way a stdlib venv does. Rather than add pip back in (which would undercut the point of this whole pip->uv migration), switch build_command itself to 'uv build' -- no pip anywhere. Verified locally through the full real uvx-wrapped PSR execution (not just uv build standalone): produces the correct dist/ artifacts with no pip involved at any point. --- pyproject.toml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pyproject.toml b/pyproject.toml index a45187b..e979892 100644 --- a/pyproject.toml +++ b/pyproject.toml @@ -93,7 +93,7 @@ local_scheme = "no-local-version" fallback_version = "0.0.0" [tool.semantic_release] -build_command = "python -m pip install --upgrade build && SETUPTOOLS_SCM_PRETEND_VERSION=$NEW_VERSION python -m build" +build_command = "SETUPTOOLS_SCM_PRETEND_VERSION=$NEW_VERSION uv build" major_on_zero = false allow_zero_version = true tag_format = "v{version}"