Release notes from litellm
Articles about Release notes from litellm
Release v1.104.3 · BerriAI/litellm
Verify Docker Image Signature All LiteLLM Docker images are signed with cosign. Every release is signed with the same key introduced in commit 0112e53. 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: 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: Expe
Release v1.106.0-rc.1 · BerriAI/litellm
Verify Docker Image Signature All LiteLLM Docker images are signed with cosign. Every release is signed with the same key introduced in commit 0112e53. Verify using the pinned commit hash (recommen
Release v1.106.0-dev.3 · BerriAI/litellm
Verify Docker Image Signature All LiteLLM Docker images are signed with cosign. Every release is signed with the same key introduced in commit 0112e53. Verify using the pinned commit hash (recommen
Release v1.105.0-rc.3 · BerriAI/litellm
Verify Docker Image Signature All LiteLLM Docker images are signed with cosign. Every release is signed with the same key introduced in commit 0112e53. Verify using the pinned commit hash (recommen
Release v1.104.2 · BerriAI/litellm
Verify Docker Image Signature All LiteLLM Docker images are signed with cosign. Every release is signed with the same key introduced in commit 0112e53. 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: 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: Expe
Release v1.105.0-rc.1 · BerriAI/litellm
Verify Docker Image Signature All LiteLLM Docker images are signed with cosign. Every release is signed with the same key introduced in commit 0112e53. Verify using the pinned commit hash (recommen
Release v1.103.3 · BerriAI/litellm
Verify Docker Image Signature All LiteLLM Docker images are signed with cosign. Every release is signed with the same key introduced in commit 0112e53. 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: 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: Expe
Release v1.105.0-dev.2 · BerriAI/litellm
Verify Docker Image Signature All LiteLLM Docker images are signed with cosign. Every release is signed with the same key introduced in commit 0112e53. Verify using the pinned commit hash (recommen
Release v1.103.2 · BerriAI/litellm
Verify Docker Image Signature All LiteLLM Docker images are signed with cosign. Every release is signed with the same key introduced in commit 0112e53. 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: 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: Expe
Release v1.103.1 · BerriAI/litellm
Verify Docker Image Signature All LiteLLM Docker images are signed with cosign. Every release is signed with the same key introduced in commit 0112e53. 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: 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: Expe
Release v1.102.2 · BerriAI/litellm
Verify Docker Image Signature All LiteLLM Docker images are signed with cosign. Every release is signed with the same key introduced in commit 0112e53. 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: 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: Expe
Release v1.101.3 · BerriAI/litellm
Verify Docker Image Signature All LiteLLM Docker images are signed with cosign. Every release is signed with the same key introduced in commit 0112e53. 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: 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: Expe
Release v1.100.4 · BerriAI/litellm
Verify Docker Image Signature All LiteLLM Docker images are signed with cosign. Every release is signed with the same key introduced in commit 0112e53. 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: 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: Expe
Release v1.104.0-rc.1 · BerriAI/litellm
Verify Docker Image Signature All LiteLLM Docker images are signed with cosign. Every release is signed with the same key introduced in commit 0112e53. Verify using the pinned commit hash (recommen
Release v1.100.3 · BerriAI/litellm
Verify Docker Image Signature All LiteLLM Docker images are signed with cosign. Every release is signed with the same key introduced in commit 0112e53. 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: 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: Expe
Release v1.101.1 · BerriAI/litellm
Verify Docker Image Signature All LiteLLM Docker images are signed with cosign. Every release is signed with the same key introduced in commit 0112e53. 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: 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: Expe
Release v1.104.0-dev.1 · BerriAI/litellm
Verify Docker Image Signature All LiteLLM Docker images are signed with cosign. Every release is signed with the same key introduced in commit 0112e53. Verify using the pinned commit hash (recommen
Release v1.103.0-dev.2 · BerriAI/litellm
Verify Docker Image Signature All LiteLLM Docker images are signed with cosign. Every release is signed with the same key introduced in commit 0112e53. Verify using the pinned commit hash (recommen
Release v1.102.0-rc.1 · BerriAI/litellm
Verify Docker Image Signature All LiteLLM Docker images are signed with cosign. Every release is signed with the same key introduced in commit 0112e53. Verify using the pinned commit hash (recommen
Release v1.106.0-dev.1 · BerriAI/litellm
Verify Docker Image Signature All LiteLLM Docker images are signed with cosign. Every release is signed with the same key introduced in commit 0112e53. Verify using the pinned commit hash (recommen
Release v1.105.0-dev.1 · BerriAI/litellm
Verify Docker Image Signature All LiteLLM Docker images are signed with cosign. Every release is signed with the same key introduced in commit 0112e53. Verify using the pinned commit hash (recommen
Release v1.104.0-rc.2 · BerriAI/litellm
Verify Docker Image Signature All LiteLLM Docker images are signed with cosign. Every release is signed with the same key introduced in commit 0112e53. Verify using the pinned commit hash (recommen
Release v1.103.0 · BerriAI/litellm
Verify Docker Image Signature All LiteLLM Docker images are signed with cosign. Every release is signed with the same key introduced in commit 0112e53. Verify using the pinned commit hash (recommen
Release v1.104.0-dev.2 · BerriAI/litellm
Verify Docker Image Signature All LiteLLM Docker images are signed with cosign. Every release is signed with the same key introduced in commit 0112e53. Verify using the pinned commit hash (recommen
Release v1.101.2 · BerriAI/litellm
Verify Docker Image Signature All LiteLLM Docker images are signed with cosign. Every release is signed with the same key introduced in commit 0112e53. 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: 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: Expe
Release v1.103.0-rc.1 · BerriAI/litellm
Verify Docker Image Signature All LiteLLM Docker images are signed with cosign. Every release is signed with the same key introduced in commit 0112e53. Verify using the pinned commit hash (recommen