litellm/.github/workflows
Lior Drihem 62b84d6aad
Prompt security litellm (#16365)
* add prompt security guardrails provider

* cosmetic

* small

* add file sanitization and update context window

* add pdf and OOXML files support

* add system prompt support

* add tests and documentation

* remove print

* fix PLR0915 Too many statements (96 > 50)

* cosmetic

* fix mypy error

* Fix failed tests due to naming conflict of responses directory with same-named pip package

* Fix mypy error: use 'aembedding' instead of 'embeddings' for async embedding call type

* Fix: Install enterprise package into Poetry virtualenv for tests

The GitHub Actions workflow was installing litellm-enterprise to system Python
using 'python -m pip install -e .', but tests run in Poetry's virtualenv using
'poetry run pytest'. This caused ImportError for enterprise package types.

Changed to 'poetry run pip install -e .' so the package is available in the
same virtualenv where pytest executes.

Fixes enterprise test collection errors in GitHub Actions CI.

* Move Prompt Security guardrail tests to tests/test_litellm/

Per reviewer feedback, move test_prompt_security_guardrails.py from
tests/guardrails_tests/ to tests/test_litellm/proxy/guardrails/ so
it will be executed by GitHub Actions workflow test-litellm.yml.

This ensures the Prompt Security integration tests run in CI.

---------

Co-authored-by: Ori Tabac <oritabac@prompt.security>
Co-authored-by: Vitaly Neyman <vitaly@prompt.security>
2025-11-24 11:44:20 -08: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
auto_update_price_and_context_window_file.py only add/update vercel ai gateway models 2025-08-04 17:22:36 -07:00
ghcr_deploy.yml feat: non-root docker hub push (#12413) 2025-07-11 08:34:32 -07:00
ghcr_helm_deploy.yml allow configuring httpx hooks for AsyncHTTPHandler (#6290) (#6415) 2024-10-24 22:00:24 -07: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 Implement GitHub Action to auto-label issues with provider keywords (#13537) 2025-08-12 21:18:20 -07:00
label-mlops.yml build: fix test 2024-12-03 12:25:36 -08:00
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 fix load test 2024-05-25 17:36:42 -07:00
locustfile.py fix load tests on litellm release notes 2025-02-26 19:11:43 -08:00
main.yml Create main.yml 2024-06-01 14:02:35 -07:00
publish-migrations.yml ci: update github action 2025-03-25 23:11:45 -07:00
read_pyproject_version.yml (ci/cd) Update read_pyproject_version.yml 2024-01-04 15:10:13 +05:30
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 fix load test 2024-05-25 17:36:42 -07: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 (fix) results_stats 2024-03-13 17:55:20 -07:00
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 test: make lint test stricter 2025-09-27 13:33:25 -07:00
test-litellm.yml Prompt security litellm (#16365) 2025-11-24 11:44:20 -08:00
test-mcp.yml perf(test-mcp.yml): run mcp tests on linting 2025-09-22 17:41:43 -07:00
update_release.py (fix) update load test result 2024-03-13 17:53:51 -07:00

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