Update pydantic-ai requirement from ==0.2.* to ==1.9.*

[dependabot]

Updates the requirements on pydantic-ai to permit the latest version.

Release notes

Sourced from pydantic-ai's releases.

v1.9.0 (2025-10-29)

What's Changed

• Support Vercel AI Data Stream Protocol by @​samuelcolvin in pydantic/pydantic-ai#2923
• Fix docs custom retry logic example by @​yf-yang in pydantic/pydantic-ai#3276

New Contributors

• @​yf-yang made their first contribution in pydantic/pydantic-ai#3276

Full Changelog: pydantic/pydantic-ai@v1.8.0...v1.9.0

Changelog

Sourced from pydantic-ai's changelog.

Upgrade Guide

In September 2025, Pydantic AI reached V1, which means we're committed to API stability: we will not introduce changes that break your code until V2 (if we do, you can shout at us as it's definitely a mistake). Once we release V2, in April 2026 at the earliest, we'll continue to provide security fixes for V1 for another 6 months minimum, so you have time to upgrade your applications.

Breaking Changes

Here's a filtered list of the breaking changes for each version to help you upgrade Pydantic AI.

v1.0.1 (2025-09-05)

The following breaking change was accidentally left out of v1.0.0:

• See #2808 - Remove Python evaluator from pydantic_evals for security reasons

v1.0.0 (2025-09-04)

• See #2725 - Drop support for Python 3.9
• See #2738 - Make many dataclasses require keyword arguments
• See #2715 - Remove cases and averages attributes from pydantic_evals spans
• See #2798 - Change ModelRequest.parts and ModelResponse.parts types from list to Sequence
• See #2726 - Default InstrumentationSettings version to 2
• See #2717 - Remove errors when passing AsyncRetrying or Retrying object to AsyncTenacityTransport or TenacityTransport instead of RetryConfig

v0.x.x

Before V1, minor versions were used to introduce breaking changes:

v0.8.0 (2025-08-26)

See #2689 - AgentStreamEvent was expanded to be a union of ModelResponseStreamEvent and HandleResponseEvent, simplifying the event_stream_handler function signature. Existing code accepting AgentStreamEvent | HandleResponseEvent will continue to work.

v0.7.6 (2025-08-26)

The following breaking change was inadvertently released in a patch version rather than a minor version:

See #2670 - TenacityTransport and AsyncTenacityTransport now require the use of pydantic_ai.retries.RetryConfig (which is just a TypedDict containing the kwargs to tenacity.retry) instead of tenacity.Retrying or tenacity.AsyncRetrying.

v0.7.0 (2025-08-12)

See #2458 - pydantic_ai.models.StreamedResponse now yields a FinalResultEvent along with the existing PartStartEvent and PartDeltaEvent. If you're using pydantic_ai.direct.model_request_stream or pydantic_ai.direct.model_request_stream_sync, you may need to update your code to account for this.

See #2458 - pydantic_ai.models.Model.request_stream now receives a run_context argument. If you've implemented a custom Model subclass, you will need to account for this.

See #2458 - pydantic_ai.models.StreamedResponse now requires a model_request_parameters field and constructor argument. If you've implemented a custom Model subclass and implemented request_stream, you will need to account for this.

v0.6.0 (2025-08-06)

This release was meant to clean some old deprecated code, so we can get a step closer to V1.

... (truncated)

Commits

• e300251 Support Vercel AI Data Stream Protocol (#2923)
• 0739a4a Don't fail after-ci deploy-docs-preview if PR docs job failed (#3287)
• 03b2271 Exclude outlines from dev group (#3285)
• 7ba1037 Fix send-tweet CI job (#3284)
• 5accf0f Disable uv cache for smokeshow as there's nothing to cache (#3283)
• e2ba27a Set GHA setup-uv cache-suffix for different package sets (#3282)
• e70e611 Fix docs custom retry logic example (#3276)
• d78ebc9 Fix agent name inference when using run_stream_events (#3279)
• cf55a71 Use latest OpenAI, Google, Anthropic models in all examples (#3278)
• c4c9e77 Respect openai_supports_tool_choice_required model profile setting in `Open...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)