* build: migrate packaging metadata to uv * ci: move automation and local tooling to uv * docker: migrate image builds and runtime setup to uv * docs: update install and deployment guidance for uv * chore: align auxiliary scripts and tests with uv * test: harden test_litellm isolation * fix: keep release and health check images self-contained * build: pin uv tooling and health check deps * test: isolate bedrock image request formatting from suite state * test: cover sandbox executor requirements flow * ci: fix circleci no-op command steps * ci: fix circleci publish workflow parsing * fix: stabilize remaining uv migration CI checks * ci: increase matrix test timeout headroom * fix: restore published docker and license coverage * fix: restore proxy runtime build parity * fix: restore proxy extras parity and venv migrations * ci: persist uv path across circleci steps * fix: keep psycopg binary in default test env * docker: preserve prisma cache across stages * test: run local proxy checks through uv python * build: restore runtime deps moved into ci * build: refresh uv lock after upstream merge * fix: restore module import in test_check_migration after merge The conflict resolution imported only the function but the test body references check_migration as a module throughout. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * fix: revert dependency promotions, remove nodejs-wheel-binaries, fix Docker layer caching - Move google-generativeai, Pillow, tenacity back to ci group (they are lazily imported and bloat the base SDK install needlessly) - Remove nodejs-wheel-binaries from extra_proxy and proxy-dev (redundant in Docker where system Node.js is already installed via apk) - Remove all nodejs-wheel node replacement and venv npm patching blocks from Dockerfiles since the wheel is no longer installed - Add --no-default-groups to CodSpeed benchmark workflow so the benchmark environment matches the old minimal pip install footprint - Apply standard uv two-phase Docker pattern: copy metadata first, install deps (cached layer), then copy source and install project - Replace CircleCI enterprise no-op with proper uv sync command Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * chore: regenerate uv.lock after removing nodejs-wheel-binaries Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * fix(ci): use cache/restore instead of cache to prevent cache poisoning The old workflow used actions/cache/restore (read-only). The uv migration changed it to actions/cache (read-write), which zizmor flags as a cache poisoning risk. Restore the safer read-only variant. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * fix(ci): disable setup-uv built-in cache to silence cache-poisoning alert The setup-uv action enables caching by default, which zizmor flags as a cache poisoning risk. Disable it since we already use a read-only cache/restore step. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * fix(ci): disable setup-uv cache in publish workflow Silences zizmor cache-poisoning alert. Publishing workflow runs infrequently on protected branches so caching adds no real benefit. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * fix(test): remove duplicate verbose_logger mock in test_check_migration The logger was patched twice — first via mocker.patch() then via mocker.patch.object(autospec=True). The second call fails because autospec cannot inspect an already-mocked attribute. Remove the redundant first patch. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> * fix(ci): free disk space before Docker build in test-server-root-path The Dockerfile.non_root build ran out of disk on the CI runner. Remove Android SDK, .NET, Boost, and GHC toolchains (~12GB) to free space. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2.9 KiB
Build & Publish litellm-proxy-extras
This runbook covers building and publishing a new version of the litellm-proxy-extras PyPI package. For use by litellm engineers only.
Prerequisites
- All
schema.prismafiles are in sync (see migration_runbook.md Step 0) - Migration has been generated and committed
- You are in the
litellm-proxy-extras/directory
Step 1: Bump the Version
Option A: Automatic Version Bump (Recommended)
Use commitizen to automatically bump the version across all files:
cd litellm-proxy-extras
cz bump --increment patch
This will automatically:
- Bump the version in
pyproject.toml(both[project].versionand[tool.commitizen].version) - Update the version in
../pyproject.toml(root) - Create a git commit with the version bump
Then skip to Step 3 (Clean Old Artifacts).
Option B: Manual Version Bump
Update the version in pyproject.toml:
cd litellm-proxy-extras
# Check current version
grep 'version' pyproject.toml
Edit pyproject.toml and bump the version (both [project].version and [tool.commitizen].version).
Step 2: Update Version in the Root Package Metadata (Manual Only)
After bumping the version in litellm-proxy-extras/pyproject.toml, you must also update the version reference in the root pyproject.toml:
| File | Line to update |
|---|---|
pyproject.toml (root) |
litellm-proxy-extras==X.Y.Z in [project.optional-dependencies].proxy |
# From the repo root — replace OLD with NEW version
sed -i '' 's/litellm-proxy-extras==OLD/litellm-proxy-extras==NEW/' pyproject.toml
Do NOT skip this step. The main
litellmpackage pins the extras version — if you don't update these, users will install the old version.
Step 3: Clean Old Artifacts
rm -rf dist/ build/ *.egg-info
Step 4: Build the Package
uv build
This creates .tar.gz and .whl files in the dist/ directory.
Verify the build output:
ls -la dist/
Step 5: Upload to PyPI
uv tool run --from 'twine==6.2.0' twine upload dist/*
You will be prompted for your PyPI API token:
Enter your API token: pypi-...
Use
__token__as the username and your PyPI API token as the password.
Quick Reference (Copy-Paste)
cd litellm-proxy-extras
rm -rf dist/ build/ *.egg-info
uv build
uv tool run --from 'twine==6.2.0' twine upload dist/*
Do you want to build and publish a new litellm-proxy-extras package? (y/n)
If yes, run the following commands in order:
cd litellm-proxy-extras
rm -rf dist/ build/ *.egg-info
uv build
uv tool run --from 'twine==6.2.0' twine upload dist/*
When twine upload runs, enter your PyPI credentials:
- Username:
__token__ - Password: (paste your PyPI API key)
If no, you're done — no package publish needed.