Skip to content

Conversation

@dsfaccini
Copy link
Collaborator

Updates mkdocstrings-python from 1.x to 2.x to fix deprecation warnings in docs build.

Changes:

  • pyproject.toml: mkdocstrings-python>=1.12.2>=2.0.0
  • mkdocs.yml: import:inventories: (required by mkdocstrings 1.0+)
  • Fixed cross-reference paths in markdown docs:
    • pydantic_ai.Agent.*pydantic_ai.agent.Agent.*
    • pydantic_evals.Dataset/Case.*pydantic_evals.dataset.*
    • pydantic_ai.Tool.*pydantic_ai.tools.Tool.*
    • pydantic_ai.RunContext.*pydantic_ai.tools.RunContext.*
    • VercelAIAdapter inherited methods → pydantic_ai.ui.UIAdapter.*
  • CLAUDE.md: Added note about macOS Cairo library path for docs build

Resolves deprecation warnings from https://github.com/pydantic/pydantic-ai/actions/runs/20134237380/job/57783147568

dsfaccini and others added 3 commits December 11, 2025 09:10
The `returns_named_value` and `returns_multiple_items` options are only
valid for the Google docstring parser. Passing them to Sphinx/Numpy
parsers now triggers a DeprecationWarning in griffe.

Also fixed cross-reference paths in docstrings to use the full module
path (e.g. `pydantic_ai.agent.Agent` instead of `pydantic_ai.Agent`).

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <[email protected]>
@DouweM
Copy link
Collaborator

DouweM commented Dec 11, 2025

@dsfaccini docs CI is failing!

@dsfaccini
Copy link
Collaborator Author

Ik!! mkdocs seems to depend on some pinned private package, this is just a sidequest, if I can figure it out with Samuel/whoever pinned the insiders we can merge otherwise it's fine

@dsfaccini
Copy link
Collaborator Author

dsfaccini commented Dec 12, 2025

So, we we're using an "insiders" version of some mkdocs packages because Pydantic was a sponsor and they had nice features. But they made the features public (very recently lol)

So I'm changing the Makefile and removing mkdocs.insiders.yml to stop using the insiders.

@DouweM I'm not allowed to modify the CI file but you can remove these lines. And the now dummy lines in the Makefile
image

All mkdocs-material and mkdocstrings-python insiders features have been
released to the public as of November 2025.

- mkdocs-material v9.7.0: All insiders features now public
- mkdocstrings-python v2.0.0: All insiders features now public

Changes:
- Remove mkdocs.insiders.yml (merge into mkdocs.yml)
- Update mkdocs-material to >=9.7.0 (for material.extensions.preview)
- Update Makefile docs-insiders to be a no-op (calls docs)
- Simplify cf-pages-build to use public packages

Sources:
- https://squidfunk.github.io/mkdocs-material/blog/2025/11/11/insiders-now-free-for-everyone/
- https://mkdocstrings.github.io/python/changelog/

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude Sonnet 4.5 <[email protected]>
@dsfaccini dsfaccini force-pushed the update-mkdocstrings-fix-crossrefs branch from fd53940 to 3940dae Compare December 12, 2025 13:30
@github-actions
Copy link

github-actions bot commented Dec 12, 2025

Docs Preview

commit: 34dee95
Preview URL: https://851213c5-pydantic-ai-previews.pydantic.workers.dev

@DouweM
Copy link
Collaborator

DouweM commented Dec 12, 2025

@dsfaccini I've updated ci.yml and Makefile!

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.

3 participants