chore(deps): update dependency pydantic-ai to >=1.47.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
pydantic-ai (changelog)	>=1.46.0 → >=1.47.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

pydantic/pydantic-ai (pydantic-ai)

v1.47.0: (2026-01-23)

Compare Source

What's Changed

🚀 Features

• Ensure thought signatures and other provider metadata survive a round trip through a Vercel AI frontend by @​Light2Dark in #​3754

New Contributors

• @​Light2Dark made their first contribution in #​3754

Full Changelog: pydantic/pydantic-ai@v1.46.0...v1.47.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[claude]

PR Review: pydantic-ai v1.47.0 Update

Summary

✅ LGTM - Safe dependency update with minimal risk

Analysis

Changes:

• Bumps pydantic-ai from >=1.46.0 to >=1.47.0 (minor version)
• Updates pydantic-ai-slim, pydantic-evals, and pydantic-graph dependencies
• Only affects the examples optional dependency group

Impact Assessment:

1. Scope: Limited to example code (examples/anthropic_comparison/mcp_optimizer_agent.py)
2. Breaking Changes: None - minor version bump with backwards compatibility
3. New Features: v1.47.0 adds metadata preservation for thought signatures in Vercel AI frontend round trips
4. Risk: Low - changes don't affect core server functionality

Code Quality:

• Lock file properly updated with correct checksums and URLs
• Version constraint uses >= allowing flexibility for future patches
• Follows project's dependency management practices

Recommendations:

• ✅ Safe to merge
• Consider running example tests if available to verify compatibility
• No code changes required

Note: Since this only affects the optional examples group and is a minor version update from the same maintainers (Pydantic team), the risk of regression is minimal.