langchain - 💡(How to fix) Fix refactor: migrate legacy pydantic .dict() to .model_dump()

Submission checklist

• This is a feature request, not a bug report or usage question.
• I added a clear and descriptive title that summarizes the feature request.
• I used the GitHub search to find a similar feature request and didn't find it.
• I checked the LangChain documentation and API reference to see if this feature already exists.
• This is not related to the langchain-community package.

Package (Required)

• langchain
• langchain-openai
• langchain-anthropic
• langchain-classic
• langchain-core
• langchain-model-profiles
• langchain-tests
• langchain-text-splitters
• langchain-chroma
• langchain-deepseek
• langchain-exa
• langchain-fireworks
• langchain-groq
• langchain-huggingface
• langchain-mistralai
• langchain-nomic
• langchain-ollama
• langchain-openrouter
• langchain-perplexity
• langchain-qdrant
• langchain-xai
• Other / not sure / general

Feature Description

"I propose migrating the deprecated Pydantic v1 .dict() method calls to the modern .model_dump() method. This ensures better compatibility with Pydantic v2 and eliminates deprecation warnings in current implementations."

Use Case

"I have identified instances where .dict() is used and am prepared to replace them with .model_dump(), ensuring all arguments (such as exclude_none or exclude_unset) are correctly mapped to their .model_dump() equivalents."

Proposed Solution

"I have identified instances where .dict() is used and am prepared to replace them with .model_dump(), ensuring all arguments (such as exclude_none or exclude_unset) are correctly mapped to their .model_dump() equivalents."

Alternatives Considered

"Ignoring the deprecation warnings, but that is not sustainable for long-term project health."

Additional Context

No response