Ashwin Bharambe 5b1e69e58e Use uv pip install instead of pip install (#921) ... ## What does this PR do? See issue: #747 -- `uv` is just plain better. This PR does the bare minimum of replacing `pip install` by `uv pip install` and ensuring `uv` exists in the environment. ## Test Plan First: create new conda, `uv pip install -e .` on `llama-stack` -- all is good. Next: run `llama stack build --template together` followed by `llama stack run together` -- all good Next: run `llama stack build --template together --image-name yoyo` followed by `llama stack run together --image-name yoyo` -- all good Next: fresh conda and `uv pip install -e .` and `llama stack build --template together --image-type venv` -- all good. Docker: `llama stack build --template together --image-type container` works!		2025-01-31 22:29:41 -08:00
..
gha_workflow_llama_stack_tests.yml	Introduce GitHub Actions Workflow for Llama Stack Tests (#523)	2024-12-04 15:42:55 -08:00
pre-commit.yml	Use uv pip install instead of pip install (#921)	2025-01-31 22:29:41 -08:00
publish-to-docker.yml	Update GH action so it correctly queries for test.pypi, etc. (#875)	2025-01-24 11:56:29 -08:00
publish-to-test-pypi.yml	Llama_Stack_Building_AI_Applications.ipynb -> getting_started.ipynb (#854)	2025-01-23 12:04:06 -08:00
tests.yml	create a github action for triggering client-sdk tests on new pull-request (#850)	2025-01-29 21:26:04 -08:00