shipfeedAI news, curated daily

01:15:58 CET
21 MAY01:15:58shipfeed
pull to refreshlast sync
Just in — 30 new
§ tools · storyline

LiteLLM v1.84.0-dev.1

LiteLLM releases v1.84.0-dev.1 with fixes for Redis GCP IAM token caching, a UI credentials endpoint correction, and a Noma v2 deepcopy crash in build scan payloads.

Apr 29 · · primary fetch1 sourceupdated Apr 29 ·

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: ```bash cosign verify \ --key https://raw.githubusercontent.com/BerriAI/litellm/0112e53046018d726492c814b3644b7d376029d0/cosign.pub \ ghcr.io/berriai/litellm:1.84.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/1.84.0-dev.1/cosign.pub \ ghcr.io/berriai/litellm:1.84.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 fix(redis): cache GCP IAM token to prevent async event loop blocking by @harish-berri in https://github.com/BerriAI/litellm/pull/26441 litellm oss branch by…

read full article on github.com
§ sources1 publication · timeline below
  1. github.comlitellm 1.84.0-dev.1primary