LiteLLM 发布: v1.102.0-dev.1

来源摘要

## Verify Docker Image Signature All LiteLLM Docker images are signed with [cosign](https://docs.sigstore.dev/cosign/overview/). Every release is signed with the same key introduced in [commit `0112e53`](https://github.com/BerriAI/litellm/commit/0112e53046018d726492c814b3644b7d376029d0). **Verify using the pinned commit hash (recommended):** A commit hash is cryptographically immutable, so this is the strongest way to ensure you are using the original signing key: ```bash cosign verify \ --key https://raw.githubusercontent.com/BerriAI/litellm/0112e53046018d726492c814b3644b7d376029d0/cosign.pub \ ghcr.io/berriai/litellm:v1.102.0-dev.1 ``` **Verify using the release tag (convenience):** Tags are protected in this repository and resolve to the same key. This option is easier to read but relies on tag protection rules: ```bash cosign verify \ --key https://raw.githubusercontent.com/BerriAI/litellm/v1.102.0-dev.1/cosign.pub \ ghcr.io/berriai/litellm:v1.102.0-dev.1 ``` Expected output: ``` The following checks were performed on each of these signatures: - The cosign claims were validated - The signatures were verified against the specified public key ``` --- ## What's Changed * feat(policy_engine): execute post_call guardrail pipelines on streaming responses by @mateo-berri in https://github.com/BerriAI/litellm/pull/38788 * fix(policy_engine): apply post_call pipeline text rewrites on streams by @mateo-berri in https://github.com/BerriAI/litellm/pull/39233 * fix(proxy): redact provider keys from pass-through failure tracebacks by @mateo-berri in https://github.com/BerriAI/litellm/pull/39964 * fix(file_search): scope emulated file_search to the request's vector stores by @mateo-berri in https://github.com/BerriAI/litellm/pull/39972 * feat(cli): add lite pi to run the pi coding