ci(e2e): restore the shared Prisma and cargo caches in the changed-tests job
Some checks failed
Terraform Provider / Provider endpoints vs proxy OpenAPI schema (push) Has been cancelled
LiteLLM Rust / rustfmt, clippy, test (push) Has been cancelled
Terraform Modules / fmt, validate, test (aws) (push) Has been cancelled
Terraform Provider / gofmt, vet, build, test (push) Has been cancelled

check_prisma_binary_cache requires every Prisma-generating job to use the
cache-prisma-binaries action and leave PRISMA_BINARY_CACHE_DIR unset, so the
engines land in the version-keyed path the action restores
This commit is contained in:
Yuneng Jiang 2026-09-01 15:58:16 -07:00
parent d216a4b162
commit c94591118a
No known key found for this signature in database

View file

@ -93,6 +93,9 @@ jobs:
with:
version: "0.10.9"
- name: Cache the Rust build
uses: ./.github/actions/cache-cargo-build
- name: Install dependencies
run: |
.github/scripts/uv_sync_with_retries.sh --frozen \
@ -101,9 +104,10 @@ jobs:
--group ci --group proxy-dev --group e2e-dev
uv pip install "pipecat-ai[openai]==1.4.0"
- name: Cache Prisma binaries
uses: ./.github/actions/cache-prisma-binaries
- name: Generate Prisma client
env:
PRISMA_BINARY_CACHE_DIR: ${{ runner.temp }}/prisma-cache
run: uv run --no-sync prisma generate --schema litellm/proxy/schema.prisma
- name: Install Playwright chromium