Skip to content

chore(deps): update dependency pydantic to v2.14.1 - #772

Merged
gadievron merged 2 commits into
masterfrom
renovate/pydantic-2.x
Oct 17, 2026
Merged

gadievron merged 2 commits into
masterfrom
renovate/pydantic-2.x

Conversation

@knostic-renovate

@knostic-renovate knostic-renovate Bot commented Oct 8, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Update Change
pydantic (changelog) minor ==2.13.5 -> ==2.14.1

Release Notes

pydantic/pydantic (pydantic)

v2.14.1: 2026-10-11

Compare Source

What's Changed
Performance
Fixes

Full Changelog: pydantic/pydantic@v2.14.0...v2.14.1

v2.14.0

Compare Source

GitHub release

What's Changed

The highlights of the v2.14 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 drops support for Python 3.9 and adds support for Python 3.15.

New Features
Changes
Fixes
New Contributors

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.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

This PR has been generated by Renovate Bot.

@knostic-renovate
knostic-renovate Bot force-pushed the renovate/pydantic-2.x branch from 512f146 to 72d9def Compare October 11, 2026 19:39
@knostic-renovate knostic-renovate Bot changed the title chore(deps): update dependency pydantic to v2.14.0 chore(deps): update dependency pydantic to v2.14.1 Oct 11, 2026
@gadievron

Copy link
Copy Markdown
Collaborator

Review at head f1f7f50c (drain batch 8, THE NEXT 20) — @sounil for visibility. Merging under the maintainer's typed class grant (ADDENDUM 6 + its addendum, memo 9791e7dfb10f7e2d, committed 35e9df58) via the admin escape hatch. repo-visibility: public · enforce_admins=false · required_reviews unmet · escape-hatch not allowance — 0 APPROVED reviews exist at this head and none was manufactured: a class grant adopts the merge, not the content (THE AUTHORITY RULING Q1, 13dbd03c).

What this PR is. pydantic==2.13.5 → 2.14.1 in libs/openant-core/requirements.txt — one line, single pin. This is the widest-blast-radius bump of the three clusters: pydantic is the validation layer the scanner's models sit on, pydantic-core is a compiled wheel (the dependency whose missing cp315 wheels are the documented reason PR #815 cannot go green on windows), and typing-inspection/annotated-types on lines 22 and 1 are its own peer deps — neither of which this PR moves, so the resolver must still be satisfied by the pinned set. CI at this head is re-polled to 19/19 before merge, and CI.yaml:66 installs from this exact file, so an unsatisfiable pin set fails the install step rather than at runtime.

Why it was blocked. Line 19 (pydantic) is adjacent to line 20 (python-dotenv), which PR #760 moves — two one-line edits inside one hunk. Nothing semantic. 772 is the first lander of cluster C in the committed order (bin/cluster-order.tsv, amendment 58, commit df0696ba): 772 then 760. The sweep at this head admits only #760 — a committed-order successor — and still blocks on anything else, on my own dirtiness against master, and on any coupled-surface guard failure.

What the two earlier clusters tonight established, which bears on #760's chances. Cluster B (816 → 814) completed exactly as granted: nothing regenerated and both landed. Cluster A did not: merging #757 freed renovate's openai branch slot, a newer version held behind the edited PR materialised as #824 within two minutes, and the regenerated centre line re-blocked #758 and #759, which are halted with their measurement. The discriminator is whether a newer version of the centre line is already available and held — so #760's fate depends on whether a pydantic newer than 2.14.1 is published and waiting. That is measured after this merge, not predicted here.

Evidence directory: runs/pr772-2026-10-17/batch8/.

@knostic-renovate

Copy link
Copy Markdown
Contributor Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@gadievron
gadievron merged commit 166d493 into master Oct 17, 2026
19 checks passed
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.

1 participant