86b71d4713
* fix: align max_tokens with max_output_tokens for consistency Fixed inconsistent max_tokens definitions in model_prices_and_context_window.json. According to LiteLLM convention, max_tokens should equal max_output_tokens when available. Models fixed: - deepseek-chat: 131072 → 8192 (now equals max_output_tokens) - dashscope/qwen-flash: 1000000 → 32768 (now equals max_output_tokens) - databricks/databricks-gemma-3-12b: 128000 → 32000 (now equals max_output_tokens) This ensures consistency across all providers where max_tokens represents the maximum number of tokens that can be generated in the output. * fix(workflow): Update issue labeling with working regex pattern - Replace contains() with regex pattern using \s* for flexible whitespace matching - Consolidate 4 separate steps into single unified component labeling step - Tested and verified pattern works for all components: SDK, Proxy, UI Dashboard, Docs - Pattern handles GitHub's issue body formatting with ### headers and variable newlines |
||
|---|---|---|
| .. | ||
| auto_update_price_and_context_window_file.py | ||
| auto_update_price_and_context_window.yml | ||
| create_daily_staging_branch.yml | ||
| ghcr_deploy.yml | ||
| ghcr_helm_deploy.yml | ||
| helm_unit_test.yml | ||
| interpret_load_test.py | ||
| issue-keyword-labeler.yml | ||
| label-component.yml | ||
| llm-translation-testing.yml | ||
| load_test.yml | ||
| locustfile.py | ||
| main.yml | ||
| publish-migrations.yml | ||
| read_pyproject_version.yml | ||
| README.md | ||
| redeploy_proxy.py | ||
| reset_stable.yml | ||
| results_stats.csv | ||
| run_llm_translation_tests.py | ||
| simple_pypi_publish.yml | ||
| stale.yml | ||
| test-linting.yml | ||
| test-litellm.yml | ||
| test-mcp.yml | ||
| update_release.py | ||
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