Skip to content

fix(azure/responses): remove invalid status param from azure call + MCP - support setting CA_BUNDLE_PATH - #15253

Merged
2 commits merged into
mainfrom
litellm_dev_10_06_2025_p2
Oct 7, 2025
Merged

2 commits merged into
mainfrom
litellm_dev_10_06_2025_p2

Conversation

@ghost

@ghost ghost commented Oct 7, 2025

Copy link
Copy Markdown

Title

Relevant issues

unsupported parameter

Pre-Submission checklist

Please complete all items before asking a LiteLLM maintainer to review your PR

  • I have Added testing in the tests/litellm/ directory, Adding at least 1 test is a hard requirement - see details
  • I have added a screenshot of my new test passing locally
  • My PR passes all unit tests on make test-unit
  • My PR's scope is as isolated as possible, it only solves 1 specific problem

Type

🆕 New Feature
🐛 Bug Fix
🧹 Refactoring
📖 Documentation
🚄 Infrastructure
✅ Test

Changes

@vercel

vercel Bot commented Oct 7, 2025 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Preview Comments Updated (UTC)
litellm Ready Ready Preview Comment Oct 7, 2025 1:37am

respect ca bundle path for mcp calls
@ghost ghost changed the title fix(azure/responses): remove invalid status param from azure call fix(azure/responses): remove invalid status param from azure call + MCP - support setting CA_BUNDLE_PATH Oct 7, 2025
@ghost
ghost merged commit 6b44156 into main Oct 7, 2025
38 of 50 checks passed
@ghost
ghost deleted the litellm_dev_10_06_2025_p2 branch October 7, 2025 03:01
fzowl pushed a commit to fzowl/litellm that referenced this pull request Jun 24, 2026
fix(azure/responses): remove invalid status param from azure call + MCP - support setting CA_BUNDLE_PATH
This pull request was closed.

This branch was successfully deployed

1 active deployment
Preview — 7f88a3f9 Deployed Oct 7, 2025 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants