From 6aaf4ad0808ec04f23f9449beb5c6e7d846ef7c1 Mon Sep 17 00:00:00 2001 From: Omar Abdelwahab Date: Wed, 12 Nov 2025 15:20:48 -0800 Subject: [PATCH] fix(ci): Remove uv.lock before sync to ensure fresh dependency resolution The uv.lock file contains cached dependency resolutions that prevent source code changes from being picked up. By removing it before uv sync, we force a fresh resolution and rebuild of dependencies. This should fix the 73 CI test failures where the resolver was loading stale method signatures without the authorization parameter. --- .github/actions/setup-runner/action.yml | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/.github/actions/setup-runner/action.yml b/.github/actions/setup-runner/action.yml index 40cecc588..9be7be591 100644 --- a/.github/actions/setup-runner/action.yml +++ b/.github/actions/setup-runner/action.yml @@ -37,11 +37,12 @@ runs: echo "Exported UV environment variables for current and subsequent steps" fi - echo "Clearing Python bytecode cache to avoid stale .pyc files" + echo "Clearing Python bytecode cache and lock file to ensure fresh install" find . -type d -name "__pycache__" -exec rm -rf {} + 2>/dev/null || true find . -name "*.pyc" -delete 2>/dev/null || true + rm -f uv.lock - echo "Updating project dependencies via uv sync" + echo "Syncing dependencies (will regenerate lock file)" uv sync --all-groups echo "Force reinstalling llama-stack from source to ensure latest changes"