[Infra] Remove unused publish_proxy_extras and prisma_schema_sync jobs from CircleCI config#25821
Conversation
publish_proxy_extras is superseded by PyPI trusted publishing (OIDC); the CircleCI project no longer has PYPI_PUBLISH_* credentials configured. prisma_schema_sync is a leaf smoke test with no dependents, and db push against the current schema is already exercised by e2e_ui_testing.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Greptile SummaryThis PR removes two CircleCI jobs that are no longer needed: Confidence Score: 5/5Safe to merge — pure deletion of two unused CI jobs with no downstream dependents. Both removed jobs are confirmed to have no No files require special attention.
|
| Filename | Overview |
|---|---|
| .circleci/config.yml | Removes publish_proxy_extras and prisma_schema_sync job definitions and their corresponding workflow entries; no remaining references to either job anywhere in the repo. |
Flowchart
%%{init: {'theme': 'neutral'}}%%
flowchart TD
BDI[build_docker_database_image] --> BAT[build_and_test]
BDI --> TBDU[test_bad_database_url]
BDI -.->|removed| PSS[~~prisma_schema_sync~~]
E2E[e2e_ui_testing] -->|covers prisma db push| DB[(PostgreSQL)]
PPE[~~publish_proxy_extras~~] -.->|removed - replaced by| OIDC[PyPI OIDC Trusted Publishing]
style PSS fill:#ffcccc,stroke:#cc0000,color:#333
style PPE fill:#ffcccc,stroke:#cc0000,color:#333
style OIDC fill:#ccffcc,stroke:#009900,color:#333
Reviews (1): Last reviewed commit: "[Infra] Remove unused publish_proxy_extr..." | Re-trigger Greptile
2f72eb6
into
litellm_internal_staging
Relevant issues
Summary
Cleaning up two CircleCI jobs that are no longer needed.
Changes
publish_proxy_extras: We now publishlitellm-proxy-extrasto PyPI via PyPI trusted publishing (OIDC-based, no long-lived token), so the CircleCI-driven publish path usingTWINE_USERNAME/PYPI_PUBLISH_USERNAME/PYPI_PUBLISH_PASSWORDis no longer used. Manually confirmed these env vars no longer exist in the CircleCI project settings, so the job cannot succeed on a delta anyway.prisma_schema_sync: This was a smoke test that booted the docker image against a fresh Postgres with--use_prisma_db_push. It is a leaf job with no downstream dependents, ande2e_ui_testingalready exercisesprisma db pushagainst the currentschema.prismaend-to-end. Dropping the duplicate saves a CI slot.No other jobs reference either of these — confirmed by grep and by checking
requires:lists.Testing
publish_proxy_extrasandprisma_schema_syncare not referenced elsewhere (norequires:dependents, no workflow entries other than their own).PYPI_PUBLISH_USERNAME/PYPI_PUBLISH_PASSWORDare no longer configured.Type
🚄 Infrastructure