The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
litellm	Ready	Preview, Comment	Mar 27, 2026 6:26pm

All committers have signed the CLA.

Merging this PR will not alter performance

✅ 16 untouched benchmarks

_{Comparing litellm_pin_prisma_node_ci (ca3457b) with main (8c2c6a4)}

Greptile Summary

This PR fixes flaky CI failures caused by prisma generate trying to download Node.js at runtime via nodeenv on GitHub Actions runners. The fix pre-installs nodejs-wheel-binaries==24.13.1 into the Poetry virtual environment before running prisma generate, mirroring the approach already used in docker/Dockerfile.non_root. A PRISMA_BINARY_CACHE_DIR env var is also added to pin the Prisma binary cache to runner.temp.\n\nBoth workflow files that call prisma generate are correctly updated — no other CI workflows use that command. The pinned version (24.13.1) is consistent across the Dockerfiles and requirements.txt.\n\nKey changes:\n- .github/workflows/test-litellm-matrix.yml — adds nodejs-wheel-binaries install + PRISMA_BINARY_CACHE_DIR before prisma generate\n- .github/workflows/test-proxy-e2e-azure-batches.yml — same fix; minor inconsistency: PRISMA_BINARY_CACHE_DIR is set only on the Generate Prisma client step, not on the subsequent Run Prisma migrations (prisma migrate deploy) step

Confidence Score: 5/5

Safe to merge — targeted infrastructure fix with no production code changes and no regressions.

All changed lines are CI workflow YAML. The fix is well-motivated, consistent with existing Dockerfile practice, and the only finding is a P2 style inconsistency (missing PRISMA_BINARY_CACHE_DIR on the migration step). Per confidence guidance, P2-only findings default to 5/5.

No files require special attention; the minor PRISMA_BINARY_CACHE_DIR inconsistency in test-proxy-e2e-azure-batches.yml is non-blocking.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[CI: Generate Prisma client step] --> B{Before fix}
    A --> C{After fix}

    B --> D[prisma generate invoked]
    D --> E[prisma detects no Node.js in venv]
    E --> F[Falls back to nodeenv]
    F --> G[Downloads Node.js from internet]
    G --> H{npm registry reachable?}
    H -- Yes --> I[npm install [email protected] succeeds]
    H -- No --> J[ECONNRESET / flaky failure]

    C --> K[pip install nodejs-wheel-binaries==24.13.1]
    K --> L[prisma generate invoked]
    L --> M[prisma detects nodejs-wheel-binaries in venv]
    M --> N[Uses bundled Node.js + npm locally]
    N --> O[prisma generate succeeds reliably]

_{Reviews (1): Last reviewed commit: "Pin nodejs-wheel-binaries in CI workflow..." | Re-trigger Greptile}