Update dependency pydantic to v2.13.1 - autoclosed#4429
Closed
renovate[bot] wants to merge 1 commit intomasterfrom
Closed
Update dependency pydantic to v2.13.1 - autoclosed#4429renovate[bot] wants to merge 1 commit intomasterfrom
renovate[bot] wants to merge 1 commit intomasterfrom
Conversation
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/pydantic-2.x
branch
2 times, most recently
from
95cafab to
563732d
Compare
dylanmtaylor
approved these changes
Apr 16, 2026
Contributor
dylanmtaylor
left a comment
dylanmtaylor
left a comment
There was a problem hiding this comment.
This should be safe to merge in as the patch for the upstream issue is fixed.
Contributor
|
Why would you just ignore my comment there? |
Contributor
Fair point, sorry about that. You're right - we should indeed wait for this to land not just upstream but also in Arch just to be on the safe side. |
Contributor
|
I wonder if there is a way to make renovate check Arch git instead of pypi for version refs so it creates bumps in step with what Arch releases... |
Contributor
|
That looks possible. |
Contributor
Let's try it. I just opened #4434 to switch from PyPi to the repology data source. It also pins exact versions instead of ranges (renovate should bump these). |
renovate
bot
force-pushed
the
renovate/pydantic-2.x
branch
2 times, most recently
from
12ef014 to
ee04996
Compare
renovate
bot
force-pushed
the
renovate/pydantic-2.x
branch
from
ee04996 to
3f0ad7b
Compare
renovate
bot
changed the title
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
==2.12.5→==2.13.1Release Notes
pydantic/pydantic (pydantic)
v2.13.1Compare Source
v2.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: Disabled by config. Please merge this manually once you are satisfied.
♻ 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 was generated by Mend Renovate. View the repository job log.