From 1ffc47499aab013c0607bff5907b73f05a0838ea Mon Sep 17 00:00:00 2001 From: Andrew Klatzke Date: Fri, 31 Jul 2026 14:59:35 -0800 Subject: [PATCH] fix: remove duplicate setup-uv from build action The build action is always preceded by the CI action in every job. Running setup-uv a second time fails when trying to activate a venv that already exists. Removed setup-uv, uv lock, and uv sync from the build action since CI already handles all three. Co-authored-by: Cursor --- .github/actions/build/action.yml | 12 ------------ 1 file changed, 12 deletions(-) diff --git a/.github/actions/build/action.yml b/.github/actions/build/action.yml index 20c5310..3141a49 100644 --- a/.github/actions/build/action.yml +++ b/.github/actions/build/action.yml @@ -9,18 +9,6 @@ inputs: runs: using: composite steps: - - uses: astral-sh/setup-uv@v5 - with: - python-version: "3.12" - - - name: Resolve lock file - shell: bash - run: uv lock - - - name: Install dependencies - shell: bash - run: uv sync --all-packages - - name: Build shell: bash run: cd ${{ inputs.workspace_path }} && uv build --out-dir dist