Repository navigation
chore(deps-dev): bump pydantic from 1.10.26 to 2.14.1 - #4068
dependabot[bot] wants to merge 1 commit into
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
Castiron custom codeEvaluated main: Trusted main policy: ✅ No new custom-code files detected. 41 mixed files remain; 0 existing customizations changed. Compared 41 existing customizations unchanged
1 more in the full report. A changed generated baseline means this report cannot reliably identify which handwritten lines changed. Inspect the custom-code diffDownload the exact patch produced by this run (requires repository access): gh run download 39846052038 --repo openai/openai-python \
--name castiron-custom-code-39846052038-1 --dir /tmp/castiron-custom-code-39846052038-1
git apply --stat /tmp/castiron-custom-code-39846052038-1/custom-code.patch
cat /tmp/castiron-custom-code-39846052038-1/custom-code.patchOr reproduce it from an SDK checkout containing the vendored reporter: git fetch --no-tags origin e8a0fd28bbdc1699c97ff0f602b1af3dd378382d eaa36bba08aff3398b52e852ca1f928134fd83eb
python3 scripts/castiron/custom_code_report.py report \
--base e8a0fd28bbdc1699c97ff0f602b1af3dd378382d \
--head eaa36bba08aff3398b52e852ca1f928134fd83eb --target-branch main --fetch --require-head-hash --public \
--out /tmp/castiron-custom-code-eaa36bba08af
cat /tmp/castiron-custom-code-eaa36bba08af/custom-code.patchThis is the current full custom patch for mixed files, not an attribution of only the handwritten lines changed by this PR. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: de0830aa92
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| ] | ||
| pydantic-v1 = ["pydantic>=1.10.26,<2"] | ||
| pydantic-v2 = ["pydantic>=2,<3"] | ||
| pydantic-v1 = ["pydantic>=1.10.26,<3"] |
There was a problem hiding this comment.
Restore the Pydantic v1 upper bound
When scripts/test-pydantic-v1 syncs this group, the new <3 constraint permits Pydantic 2.13.5; correspondingly, the regenerated uv.lock contains only 2.13.5. The supposed v1 test pass therefore runs the v2 suite again and stops protecting the SDK's advertised Pydantic v1 compatibility, so this group must retain its <2 bound and separate locked v1 resolution.
AGENTS.md reference: AGENTS.md:L31-L34
Useful? React with 👍 / 👎.
| [[package]] | ||
| name = "openai" | ||
| version = "3.29.0" # x-release-please-version | ||
| version = "3.29.0" |
There was a problem hiding this comment.
Preserve the release-please version marker
Removing this comment makes the Verify dependency groups and committed lock step in .github/workflows/ci.yml fail its explicit marker assertion on every run. It also removes the marker used for the configured uv.lock release version update, so retain # x-release-please-version on this line.
Useful? React with 👍 / 👎.
2852ce9 to
315550c
Compare
4beaca7 to
06ff2a4
Compare
48aa0d0 to
8761017
Compare
Bumps [pydantic](https://github.com/pydantic/pydantic) from 1.10.26 to 2.14.1. - [Release notes](https://github.com/pydantic/pydantic/releases) - [Changelog](https://github.com/pydantic/pydantic/blob/main/HISTORY.md) - [Commits](pydantic/pydantic@v1.10.26...v2.14.1) --- updated-dependencies: - dependency-name: pydantic dependency-version: 2.13.5 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
8761017 to
eaa36bb
Compare
|
Thanks for the update! This group intentionally tests Pydantic v1, and upgrading it to v2 would remove that coverage. We already test v2 separately, so I’m closing this update. |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
Bumps pydantic from 1.10.26 to 2.14.1.
Release notes
Sourced from pydantic's releases.
... (truncated)
Changelog
Sourced from pydantic's changelog.
... (truncated)
Commits
b2212c7Prepare release v2.14.1968fb2bFix docs conversion table6adc8b3Support named tuples inSequencevalidation7637fbcReject out-of-range int inputs fortimedeltadfdbfcbEnforce themax_digitswhole-digits limit in the PythonDecimalvalidatore2456d3Supportclosedandextra_itemsvia inheritance inTypedDict317655dHarden CI security3ba1dd4FixTypeErroronForwardRefon Python 3.10.043681abBumpsamuelcolvin/check-python-versionaction to v5.1d6bc53aAvoid unnecessary extra dict allocation in model validation