chore: litellm upstream version

[Vedantsahai18]

PR Type

enhancement

---

Description

• Updated the Docker image reference in docker-compose.yml.

• Changed the image source to ghcr.io/berriai with version main-v1.57.0.

---

Changes walkthrough 📝

	Relevant files
Configuration changes	docker-compose.yml Update Docker image reference and source                                  llm-proxy/docker-compose.yml Updated the Docker image reference. Commented out the old image reference. Changed the image source to ghcr.io/berriai with version main-v1.57.0. +2/-1

---

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

---

Important

Update litellm-base image in docker-compose.yml to ghcr.io/berriai/litellm-database:main-v1.57.0.

• Docker Image Update:
  • In docker-compose.yml, update litellm-base image from julepai/litellm-database:fix_anthropic_tool_image_content-amd64 to ghcr.io/berriai/litellm-database:main-v1.57.0.

^{This description was created by for 8083b85. It will automatically update as commits are pushed.}

[qodo-merge-pro-for-open-source]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 1 🔵⚪⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ No major issues detected

[ellipsis-dev]

👍 Looks good to me! Reviewed everything up to 8083b85 in 9 seconds

More details

• Looked at 14 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 1 drafted comments based on config settings.

1. llm-proxy/docker-compose.yml:5

• Draft comment:
  Ensure that the new image ghcr.io/berriai/litellm-database:main-v1.57.0 is compatible with the existing configuration and services. Test thoroughly to confirm no breaking changes.
• Reason this comment was not posted:
  Confidence changes required: 50%
  The PR changes the image source for the litellm-database service. This is a straightforward change, but it's important to ensure that the new image is compatible with the existing setup.

Workflow ID: wflow_HbcU48fYTkyb8oDI

---

You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

[qodo-merge-pro-for-open-source]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Score
General	Use immutable image references by pinning to SHA hash instead of mutable version tags Pin the Docker image to a specific SHA hash instead of using a version tag to ensure immutable and reproducible builds. llm-proxy/docker-compose.yml [5] -image: ghcr.io/berriai/litellm-database:main-v1.57.0 +image: ghcr.io/berriai/litellm-database@sha256:<specific-sha256-hash> Apply this suggestion Suggestion importance[1-10]: 8 Why: Using SHA hash pinning for Docker images is a critical security and reliability best practice, as it prevents supply chain attacks and ensures reproducible builds by avoiding mutable tags that can point to different images over time.	8

[standard-input]

No issues flagged.
Standard Input can make mistakes. Check important info.