LiteLLM 1.104

Apply this prompt to the LiteLLM 1.104 SDK and proxy. Treat the proxy as a credentialed gateway with its own authorization and storage rules, even when an application already authenticated the caller.

Boot and credentials

• Use a security-supported CPython minor accepted by the package's >=3.10,<3.15 metadata and test selected extras on it. Review PyPI and container artifacts separately; verify an image signature against the release's trusted cosign key and deploy the verified digest.
• Set a strong random LITELLM_MASTER_KEY in protected runtime configuration; leave LITELLM_DANGEROUSLY_PERMIT_WEAK_OR_UNSET_MASTER_KEY and dangerously_permit_weak_or_unset_master_key disabled. Keep the master key out of client SDKs, logs, and browser code.
• Preserve the separate LITELLM_SALT_KEY when rotating the master key, and use the documented migration mechanism for database values encrypted with an old master key. Store provider and MCP credentials in protected secret storage; scope each upstream credential to its intended provider or server.
• Keep ENFORCE_PRISMA_MIGRATION_CHECK enabled and stop serving if database setup fails. Run schema migration with a controlled identity before accepting traffic; do not turn database errors into authenticated but unbounded access.

Keys and sessions

• Generate one expiring virtual key per application or service, with narrow models, allowed_routes, team_id, and object_permission. Empty models, *, and proxy-admin roles are broad grants; confirm effective rights with denied-model and denied-route tests.
• Authenticate