litellm/.github/workflows
Cesar Garcia 7515f179e7
fix: sync Helm chart version with LiteLLM release version (#19438)
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/
2026-01-20 14:13:26 -08:00
..
auto_update_price_and_context_window_file.py only add/update vercel ai gateway models 2025-08-04 17:22:36 -07:00
auto_update_price_and_context_window.yml bring back model_prices_and_context_window update yml job 2024-08-20 12:09:54 -07:00
check_duplicate_issues.yml ci(github): add automated duplicate issue checker and template safeguards (#19218) 2026-01-17 00:17:20 +05:30
create_daily_staging_branch.yml Add workflow to create daily staging branches (#18020) 2025-12-16 08:13:54 +05:30
ghcr_deploy.yml fix: sync Helm chart version with LiteLLM release version (#19438) 2026-01-20 14:13:26 -08:00
ghcr_helm_deploy.yml fix: sync Helm chart version with LiteLLM release version (#19438) 2026-01-20 14:13:26 -08:00
helm_unit_test.yml ci: add helm unittest 2025-03-08 01:29:25 +01:00
interpret_load_test.py fix workflow 2025-10-18 11:14:18 -07:00
issue-keyword-labeler.yml Improve issue labeling: add component dropdown and more provider keywords (#17957) 2025-12-16 09:38:39 +05:30
label-component.yml feat: add auto-labeling for 'claude code' issues (#19242) 2026-01-17 03:31:48 +05:30
llm-translation-testing.yml feat: add local LLM translation testing with artifact generation (#12120) 2025-06-27 21:24:19 -07:00
load_test.yml
locustfile.py Revert "[Fix] Security - Remove example API keys with high entropy (#18255)" 2025-12-20 20:48:11 +05:30
main.yml Create main.yml 2024-06-01 14:02:35 -07:00
publish-migrations.yml fix: prevent Prisma migration workflow from running in forks (#18863) 2026-01-09 22:56:32 +05:30
read_pyproject_version.yml
README.md build(github/manual_pypi_publish.yml): manual workflow to publish pip package - used for pushing dev releases (#12985) 2025-07-25 09:26:47 -07:00
redeploy_proxy.py
reset_stable.yml ci(reset_stable.yml): fix to run on release created events 2024-12-28 19:53:18 -08:00
results_stats.csv
run_llm_translation_tests.py feat: add local LLM translation testing with artifact generation (#12120) 2025-06-27 21:24:19 -07:00
simple_pypi_publish.yml build(github/manual_pypi_publish.yml): manual workflow to publish pip package - used for pushing dev releases (#12985) 2025-07-25 09:26:47 -07:00
stale.yml fix stale issue mgmt 2025-01-27 18:56:02 -08:00
test-linting.yml add a new feature fix to expose the team alias when authenticating th… (#17725) 2025-12-10 10:10:28 -08:00
test-litellm.yml Normalize OpenAI SDK BaseModel choices/messages to avoid Pydantic serializer warnings (#18972) 2026-01-14 03:40:11 +05:30
test-mcp.yml test: Pydantic version up 2026-01-20 10:49:33 +09:00
update_release.py

Simple PyPI Publishing

A GitHub workflow to manually publish LiteLLM packages to PyPI with a specified version.

How to Use

  1. Go to the Actions tab in the GitHub repository
  2. Select Simple PyPI Publish from the workflow list
  3. Click Run workflow
  4. Enter the version to publish (e.g., 1.74.10)

What the Workflow Does

  1. Updates the version in pyproject.toml
  2. Copies the model prices backup file
  3. Builds the Python package
  4. 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