chore(deps): update dependency pydantic to v2.13.4 #48
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/pydantic-2.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
==2.12.5→==2.13.4Release Notes
pydantic/pydantic (pydantic)
v2.13.4Compare Source
GitHub release
What's Changed
Packaging
pydantic-corelinker flags on macOS by @washingtoneg and @Viicos in #13147Fixes
RootModelcore metadata by @Viicos in #13129v2.13.3Compare Source
GitHub release
What's Changed
Fixes
AttributeErrorsubclasses withfrom_attributesby @Viicos in #13096v2.13.2Compare Source
GitHub release
What's Changed
Fixes
ValidationInfo.field_namemissing withmodel_validate_json()by @Viicos in #13084v2.13.1Compare Source
GitHub release
What's Changed
Fixes
ValidationInfo.datamissing withmodel_validate_json()by @davidhewitt in #13079v2.13.0Compare Source
GitHub release
The highlights of the v2.13 release are available in the blog post.
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.
This release contains the updated
pydantic.v1namespace, matching version 1.10.26 which includes support for Python 3.14.What's Changed
See the beta releases for all changes sinces 2.12.
New Features
Changes
Fixes
Anywhen synthesizing_build_sourcesforBaseSettings.__init__()signature in the mypy plugin by @Viicos in #13049extraconfiguration by @Viicos in #13062Packaging
New Contributors
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate.
d63fca81a67c9b1ab34a7c9b1ab34a998a1d943b998a1d943b5b087abd365b087abd36efca9b9f4defca9b9f4d7dfe6ed0227dfe6ed0222abe73af012abe73af018bb22836b48bb22836b49ce0e73bee9ce0e73bee7d2dba2cc07d2dba2cc0b001f564f1b001f564f1761e2d49ab761e2d49ab5d403f7d855d403f7d85ae3f9aade6ae3f9aade6570c260ec9570c260ec9266b9b4d21266b9b4d217e4172a6377e4172a637032684e090032684e090ac9eac9c35ac9eac9c35841a53b5aa841a53b5aa00612df5ce00612df5ce4de4631e374de4631e377f38bdc0277f38bdc0272df15c872e2df15c872e89927ad95789927ad957cc5b9f269bcc5b9f269b7e65a0f5d87e65a0f5d833ffe419cb33ffe419cb5642fa04d15642fa04d1f5145412f2Superseded by #179 (fixes #178) — closing.
This update is already in
main:bot/requirements.txtnow pinspydantic==2.13.4, exactly what this PR proposed.This PR couldn't merge on its own because
bot/requirements.txtis a pip-compile lockfile and pydantic pinspydantic-coreto an exact version. Thepip_requirementsmanager bumped only thepydanticline, leavingpydantic-core==2.41.5behind:#179 regenerated the lock so both moved together (
pydantic 2.13.4+pydantic-core 2.46.4), and switched this file to Renovate'spip-compilemanager so future pydantic updates regenerate the lock instead of decoupling the pair. Verified: installs cleanly, 186 bot tests pass, CI green.Pull request closed