litellm/.github/workflows
Ryan Crabbe c7d3198d9a fix: pass prompt as env var in duplicate detection workflows
Fixes "Input must be provided either through stdin or as a prompt
argument" error by moving the prompt to a PROMPT env variable
instead of inline multiline shell string.
2026-02-21 14:29:08 -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
check_duplicate_issues.yml fix: pass prompt as env var in duplicate detection workflows 2026-02-21 14:29:08 -08:00
check_duplicate_prs.yml fix: pass prompt as env var in duplicate detection workflows 2026-02-21 14:29:08 -08:00
create_daily_staging_branch.yml fix: change oss staging branch name to reflect they're oss 2026-01-22 11:50:27 -08:00
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
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
regenerate-poetry-lock.yml fix(ci): drop PAT_TOKEN_2 approval step, use github.token for auto-merge 2026-02-19 21:17:40 -03:00
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_server_root_path.yml adjusting the server root path test to non root image 2026-02-18 11:56:10 -08:00
test-linting.yml Remove validate job from lint 2026-01-29 16:26:00 +05:30
test-litellm-matrix.yml ci: further split b2/b3 to isolate single heavy files 2026-02-20 14:08:25 -03:00
test-litellm-ui-build.yml adding timeout 2026-02-14 13:53:21 -08:00
test-litellm.yml fix(ci): install enterprise package into main project venv, not enterprise's own venv 2026-02-18 21:24:06 -03:00
test-mcp.yml fix(ci): install enterprise package into main project venv, not enterprise's own venv 2026-02-18 21:24:06 -03:00
test-model-map.yaml Correct model map path 2026-01-29 16:33:50 +05:30
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