mirror of
https://github.com/tiennm99/litellm.git
synced 2026-06-23 23:40:07 +00:00
24ead9b4e1
Running `cd enterprise && poetry run pip install -e .` causes poetry to create a separate venv in `enterprise/.venv` (since enterprise/ has its own pyproject.toml). The main project's tests run with `.venv/bin/python`, so the enterprise package installed in `enterprise/.venv` is never seen. Fix: run `poetry run pip install -e enterprise/` from the repo root so poetry uses the main project's venv. This ensures litellm_enterprise is importable when tests run. This explains why enterprise tests kept failing with: AttributeError: '_PROXY_LiteLLMManagedFiles' object has no attribute '_check_file_deletion_allowed' even after --force-reinstall was added — the reinstall was going to the wrong virtual environment. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Simple PyPI Publishing
A GitHub workflow to manually publish LiteLLM packages to PyPI with a specified version.
How to Use
- Go to the Actions tab in the GitHub repository
- Select Simple PyPI Publish from the workflow list
- Click Run workflow
- Enter the version to publish (e.g.,
1.74.10)
What the Workflow Does
- Updates the version in
pyproject.toml - Copies the model prices backup file
- Builds the Python package
- Publishes to PyPI
Prerequisites
Make sure the following secret is configured in the repository:
PYPI_PUBLISH_PASSWORD: PyPI API token for authentication
Example Usage
- Version:
1.74.11→ Publishes as v1.74.11 - Version:
1.74.10-hotfix1→ Publishes as v1.74.10-hotfix1
Features
- ✅ Manual trigger with version input
- ✅ Automatic version updates in
pyproject.toml - ✅ Repository safety check (only runs on official repo)
- ✅ Clean package building and publishing
- ✅ Success confirmation with PyPI package link