Skip to content

Update pydantic to 2.13.0 #515

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
jan-janssen merged 2 commits into from
Apr 13, 2026
Merged

Update pydantic to 2.13.0 #515

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
375ce7f
Update pydantic to 2.13.0
jan-janssen Apr 13, 2026
5af1789
Add pydantic to mybinder
jan-janssen Apr 13, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .ci_support/environment-docs.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,6 @@ dependencies:
- tqdm =4.67.3
- jupyter-book =1.0.0
- python =3.12
- pydantic =2.12.5
- pydantic =2.13.0
Copy link
Copy Markdown

@coderabbitai coderabbitai bot Apr 13, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🔴 Critical

🧩 Analysis chain

🌐 Web query:

Verify Pydantic 2.13.0 compatibility notes for documentation tooling contexts (import-time behavior, deprecations, or config changes that could affect Sphinx/autodoc builds).

💡 Result:

As of April 13, 2026, the upstream pydantic repo does not show a final v2.13.0 tag—only v2.13.0b1 (Feb 23, 2026), v2.13.0b2 (Feb 24, 2026), and v2.13.0b3 (Mar 31, 2026). [1]

Documentation-tooling–relevant compatibility notes seen in the 2.13.0 beta release notes (i.e., things that can affect Sphinx/autodoc import + signature rendering) include:

  • Reduced eager annotation evaluation during signature/introspection logic: 2.13.0b1 includes “Do not eagerly evaluate annotations in signature logic”, which can change import-time behavior and can prevent failures when annotations reference optional/unavailable imports during autodoc runs. [2]
  • Better diagnostics when using ImportString: 2.13.0b1 notes “Improve ImportString error when internal imports fail”, which can change the exception/warning surface you see in autodoc builds that import modules. [2]
  • Packaging/layout change: 2.13.0b1 states the pydantic-core repository was merged into the main pydantic repo (“Import pydantic-core into pydantic”). This is unlikely to change your runtime imports (pydantic_core is still a dependency), but it can affect how you trace/build/debug native-wheel issues in doc build environments. [2]
  • Backported pydantic.v1 namespace fix (beta): 2.13.0b2 includes “Fix backported V1 namespace”, relevant if autodoc imports pydantic.v1 for legacy docs. [3]

Deprecations/config behaviors that commonly break doc builds (especially when Sphinx is run with -W / “warnings as errors”) still apply in the v2 line (not unique to 2.13), notably:

  • Pydantic v2 retains deprecated APIs that emit DeprecationWarning, and specifically mentions that the v1-style behavior involving an inner Config class on models is deprecated—either of which can fail documentation builds if warnings are treated as errors. [4]

Sources:
[1] Pydantic GitHub tags/releases list showing only 2.13.0 beta tags (no final 2.13.0). (github.com)
[2] Pydantic v2.13.0b1 release notes (signature/annotation evaluation, ImportString error improvements, pydantic-core merge). (github.com)
[3] Pydantic v2.13.0b2 release notes (backported V1 namespace fix). (github.com)
[4] Pydantic migration guide (deprecation warnings; deprecation around Config/config behavior). (pydantic.dev)

Citations:

Pydantic v2.13.0 does not have a final release yet—only beta versions (b1, b2, b3) exist as of April 2026.

Pinning to pydantic =2.13.0 will cause package resolution to fail. As of April 13, 2026, the Pydantic repository shows only beta tags (v2.13.0b1, v2.13.0b2, v2.13.0b3); no final v2.13.0 has been released.

If the intent is to use the latest beta, explicitly pin to a beta version (e.g., =2.13.0b3). Otherwise, use a stable released version or wait for the final v2.13.0 release.

🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In @.ci_support/environment-docs.yml at line 16, The pinned dependency line
"pydantic =2.13.0" references a non-existent final release; change the pin to a
valid release specifier—either explicitly target the latest beta (e.g.,
"pydantic =2.13.0b3") if you intend a beta, or switch to a known-stable version
(for example "pydantic =2.12.x" or a specific stable like "pydantic =2.12.5") so
package resolution will succeed; update the dependency string accordingly
wherever "pydantic =2.13.0" appears.

- hatchling =1.29.0
- hatch-vcs =0.5.0
2 changes: 1 addition & 1 deletion .ci_support/environment.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,4 +10,4 @@ dependencies:
- tqdm =4.67.3
- hatchling =1.29.0
- hatch-vcs =0.5.0
- pydantic =2.12.5
- pydantic =2.13.0
1 change: 1 addition & 0 deletions binder/environment.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,3 +11,4 @@ dependencies:
- tqdm =4.67.3
- hatchling =1.29.0
- hatch-vcs =0.5.0
- pydantic =2.13.0
2 changes: 1 addition & 1 deletion pyproject.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -50,7 +50,7 @@ remote = [
"tqdm==4.67.3",
]
twofactor = ["pyauthenticator==0.3.0"]
pydantic = ["pydantic==2.12.5"]
pydantic = ["pydantic==2.13.0"]

[project.scripts]
pysqa = "pysqa.cmd:command_line"
Expand Down
Loading