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.
This commit is contained in:
Omar Abdelwahab 2025-11-12 15:20:48 -08:00
parent 1ea57b0a17
commit 6aaf4ad080

View file

@ -37,11 +37,12 @@ runs:
echo "Exported UV environment variables for current and subsequent steps" echo "Exported UV environment variables for current and subsequent steps"
fi 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 . -type d -name "__pycache__" -exec rm -rf {} + 2>/dev/null || true
find . -name "*.pyc" -delete 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 uv sync --all-groups
echo "Force reinstalling llama-stack from source to ensure latest changes" echo "Force reinstalling llama-stack from source to ensure latest changes"