shipfeedAI news, curated daily

18:48:24 CET
26 AUG18:48:24shipfeed
pull to refreshlast sync
Just in — 30 new
§ langchain · storyline

Verifies Docker images with cosign signatures

LiteLLM Docker images are signed with cosign for cryptographic verification.

Aug 3 · · primary fetch1 sourceupdated Aug 3 ·

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:v1.96.0-rc.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.96.0-rc.1/cosign.pub \ ghcr.io/berriai/litellm:v1.96.0-rc.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(mcp): annotate connected-app reachability on the gateway connect page by @tin-berri in https://github.com/BerriAI/litellm/pull/34867 fix(mcp): recover the…

read full article on github.com
§ sources2 publications · timeline below
  1. github.comLiteLLM v1.96.0-rc.1primary
  2. github.comLiteLLM v1.94.1

§ how this story moved

  1. primaryLiteLLM — Releases publishes the launch post.
  2. LiteLLM — Releases picks up coverage.