mirror of
https://github.com/tiennm99/litellm.git
synced 2026-06-18 00:48:01 +00:00
Cesar Garcia
7515f179e7
Replace independent auto-incrementing chart versioning with 1-1 sync to LiteLLM version. This allows users to easily map Helm chart versions to LiteLLM versions without needing to inspect appVersion. Changes: - Remove auto-increment logic that read from OCI registry - Chart version now equals LiteLLM tag without 'v' prefix (v1.81.0 -> 1.81.0) - appVersion equals full Docker tag (v1.81.0) - Update both ghcr_deploy.yml and ghcr_helm_deploy.yml workflows Before: helm chart 0.1.837 -> user has to guess LiteLLM version After: helm chart 1.81.0 -> matches LiteLLM v1.81.0 References: - https://codefresh.io/docs/docs/ci-cd-guides/helm-best-practices/
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