Skip to content

Comments

Update pydantic#69

Open
uniproject-renovate[bot] wants to merge 1 commit intomainfrom
renovate/pydantic
Open

Update pydantic#69
uniproject-renovate[bot] wants to merge 1 commit intomainfrom
renovate/pydantic

Conversation

@uniproject-renovate
Copy link
Contributor

@uniproject-renovate uniproject-renovate bot commented Jan 23, 2026

This PR contains the following updates:

Package Change Age Confidence
pydantic (changelog) ==2.11.7==2.12.5 age confidence
pydantic-core ==2.33.2==2.42.0 age confidence
pydantic_core ==2.33.2==2.42.0 age confidence

Release Notes

pydantic/pydantic (pydantic)

v2.12.5

Compare Source

GitHub release

This is the fifth 2.12 patch release, addressing an issue with the MISSING sentinel and providing several documentation improvements.

The next 2.13 minor release will be published in a couple weeks, and will include a new polymorphic serialization feature addressing
the remaining unexpected changes to the serialize as any behavior.

  • Fix pickle error when using model_construct() on a model with MISSING as a default value by @​ornariece in #​12522.
  • Several updates to the documentation by @​Viicos.

v2.12.4

Compare Source

GitHub release

This is the fourth 2.12 patch release, fixing more regressions, and reverting a change in the build() method
of the AnyUrl and Dsn types.

This patch release also fixes an issue with the serialization of IP address types, when serialize_as_any is used. The next patch release
will try to address the remaining issues with serialize as any behavior by introducing a new polymorphic serialization feature, that
should be used in most cases in place of serialize as any.

v2.12.3

Compare Source

GitHub release

What's Changed

This is the third 2.12 patch release, fixing issues related to the FieldInfo class, and reverting a change to the supported
after model validator function signatures.

  • Raise a warning when an invalid after model validator function signature is raised by @​Viicos in #​12414.
    Starting in 2.12.0, using class methods for after model validators raised an error, but the error wasn't raised concistently. We decided
    to emit a deprecation warning instead.
  • Add FieldInfo.asdict() method, improve documentation around FieldInfo by @​Viicos in #​12411.
    This also add back support for mutations on FieldInfo classes, that are reused as Annotated metadata. However, note that this is still
    not a supported pattern. Instead, please refer to the added example in the documentation.

The blog post section on changes was also updated to document the changes related to serialize_as_any.

v2.12.2

Compare Source

GitHub release

What's Changed
Fixes
  • Release a new pydantic-core version, as a corrupted CPython 3.10 manylinux2014_aarch64 wheel got uploaded (pydantic-core#1843).
  • Fix issue with recursive generic models with a parent model class by @​Viicos in #​12398

v2.12.1

Compare Source

GitHub release

What's Changed

This is the first 2.12 patch release, addressing most (but not all yet) regressions from the initial 2.12.0 release.

Fixes
New Contributors

v2.12.0

Compare Source

GitHub release

What's Changed

This is the final 2.12 release. It features the work of 20 external contributors and provides useful new features, along with initial Python 3.14 support.
Several minor changes (considered non-breaking changes according to our versioning policy)
are also included in this release. Make sure to look into them before upgrading.

Note that Pydantic V1 is not compatible with Python 3.14 and greater.

Changes (see the alpha and beta releases for additional changes since 2.11):

Packaging
New Features
Fixes
New Contributors

v2.11.10

Compare Source

GitHub release

What's Changed
Fixes

v2.11.9

Compare Source

GitHub release

What's Changed
Fixes

v2.11.8

Compare Source

GitHub release

What's Changed
Fixes
pydantic/pydantic-core (pydantic-core)

v2.41.5

Compare Source

What's Changed
New Contributors

Full Changelog: pydantic/pydantic-core@v2.41.4...v2.41.5

v2.41.4

Compare Source

v2.41.3

Compare Source

v2.41.2: 2025-10-13

Compare Source

What's Changed
New Contributors

Full Changelog: pydantic/pydantic-core@v2.41.1...v2.41.2

v2.41.1: 2025-10-06

Compare Source

What's Changed

Full Changelog: pydantic/pydantic-core@v2.41.0...v2.41.1

v2.41.0: 2025-10-06

Compare Source

What's Changed
New Contributors

Full Changelog: pydantic/pydantic-core@v2.40.1...v2.41.0

v2.40.1: 2025-10-02

Compare Source

What's Changed

Full Changelog: pydantic/pydantic-core@v2.40.0...v2.40.1

v2.40.0: 2025-10-01

Compare Source

What's Changed
New Contributors

Full Changelog: pydantic/pydantic-core@v2.39.0...v2.40.0

v2.39.0: 2025-08-11

Compare Source

What's Changed

Full Changelog: pydantic/pydantic-core@v2.38.0...v2.39.0

v2.38.0: 2025-08-04

Compare Source

What's Changed
New Contributors

Full Changelog: pydantic/pydantic-core@v2.37.2...v2.38.0

v2.37.2: 2025-07-26

Compare Source

What's Changed

Full Changelog: pydantic/pydantic-core@v2.37.1...v2.37.2

v2.37.1: 2025-07-25

Compare Source

What's Changed

Identical to v2.37.0.

v2.37.0: 2025-07-25

Compare Source

What's Changed

Full Changelog: pydantic/pydantic-core@v2.36.0...v2.37.0

v2.36.0: 2025-07-23

Compare Source

What's Changed

Full Changelog: pydantic/pydantic-core@v2.35.2...v2.36.0

v2.35.2: 2025-06-26

Compare Source

What's Changed

Full Changelog: pydantic/pydantic-core@v2.35.1...v2.35.2

v2.35.1: 2025-06-11

Compare Source

What's Changed

Full Changelog: pydantic/pydantic-core@v2.35.0...v2.35.1

v2.35.0: 2025-06-11

Compare Source

What's Changed
New Contributors

Full Changelog: pydantic/pydantic-core@v2.34.1...v2.35.0

v2.34.1

Compare Source

v2.34.0: 2025-04-17

Compare Source

What's Changed
New Contributors

Full Changelog: pydantic/pydantic-core@v2.33.1...v2.34.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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

This PR has been generated by Renovate Bot.

@uniproject-renovate uniproject-renovate bot added kind/dependency-update 依存関係の更新 renovate/python (renovate) dependency update of python type/minor (renovate) minor update labels Jan 23, 2026
@uniproject-renovate uniproject-renovate bot force-pushed the renovate/pydantic branch 3 times, most recently from be3e8af to c170b51 Compare January 23, 2026 23:01
@uniproject-renovate
Copy link
Contributor Author

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: src/uv.lock
Command failed: uv lock --upgrade-package pydantic --upgrade-package pydantic-core
Using CPython 3.14.2 interpreter at: /opt/containerbase/tools/python/3.14.2/bin/python3.14
  × No solution found when resolving dependencies for split (markers:
  │ python_full_version >= '3.13'):
  ╰─▶ Because pydantic==2.12.5 depends on pydantic-core==2.41.5 and your
      project depends on pydantic==2.12.5, we can conclude that your project
      depends on pydantic-core==2.41.5.
      And because your project depends on pydantic-core==2.42.0, we can
      conclude that your project's requirements are unsatisfiable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

kind/dependency-update 依存関係の更新 renovate/python (renovate) dependency update of python type/minor (renovate) minor update

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants