Upgrade pydantic properly via uv pip compile

[Copilot]

PR #3003 only bumped pydantic-core (2.41.5 → 2.42.0) without updating pydantic, causing an unsatisfiable dependency conflict: pydantic==2.12.5 pins pydantic-core==2.41.5 exactly.

Changes

• Re-ran uv pip compile with --upgrade-package pydantic --upgrade-package pydantic-core to upgrade both atomically
• pydantic stays at 2.12.5 and pydantic-core stays at 2.41.5 — correct, since pydantic 2.13.0 (which requires pydantic-core 2.42.0) only has beta releases
• Compile also refreshed transitive dependency annotations (added async-timeout, exceptiongroup, taskgroup, tomli; cleaned up httpx[http2] → httpx and pyjwt[crypto] → pyjwt extras)

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• releases.astral.sh
  • Triggering command: /home/REDACTED/.local/bin/uv uv pip compile requirements.in -o /tmp/requirements_new.txt --python-version 3.10 --upgrade-package pydantic --upgrade-package pydantic-core (dns block)
• test-cosmosdb-account.documents.azure.com
  • Triggering command: /home/REDACTED/work/azure-search-openai-demo/azure-search-openai-demo/.venv/bin/pytest pytest tests/ -x -q --ignore=tests/e2e.py --ignore=tests/test_app.py (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[pamelafox]

@copilot This PR does not seem to actually upgrade Pydantic then?