public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Benjamin A. Beasley <code@musicinmybrain.net>
To: git-commits@fedoraproject.org
Subject: [rpms/python-pydantic-core] f45: Allow jiter 0.19
Date: Sat, 07 Nov 2026 08:22:41 GMT [thread overview]
Message-ID: <179403976108.1.3677025605058335629.rpms-python-pydantic-core-f35b5da76e3c@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/python-pydantic-core
Branch : f45
Commit : f35b5da76e3cc1965b86eb418431affed13aace5
Author : Benjamin A. Beasley <code@musicinmybrain.net>
Date : 2026-11-06T23:57:43+00:00
Stats : +7/-7 in 2 file(s)
URL : https://src.fedoraproject.org/rpms/python-pydantic-core/c/f35b5da76e3cc1965b86eb418431affed13aace5?branch=f45
Log:
Allow jiter 0.19
---
diff --git a/pydantic-core-fix-metadata.diff b/pydantic-core-fix-metadata.diff
index 4ba09aa..3aac9c7 100644
--- a/pydantic-core-fix-metadata.diff
+++ b/pydantic-core-fix-metadata.diff
@@ -18,7 +18,7 @@ diff -Naur a/Cargo.toml b/Cargo.toml
num-traits = "0.2.19"
uuid = "1.23.0"
-jiter = { version = "0.14.0", features = ["python"] }
-+jiter = { version = ">=0.14.0, <0.19.0", features = ["python"] }
++jiter = { version = ">=0.14.0, <0.20.0", features = ["python"] }
hex = "0.4.3"
percent-encoding = "2.3.2"
hashbrown = { version = "0.16", default-features = false, features = ["inline-more"] }
diff --git a/python-pydantic-core.spec b/python-pydantic-core.spec
index e82baa1..ad6d263 100644
--- a/python-pydantic-core.spec
+++ b/python-pydantic-core.spec
@@ -19,12 +19,12 @@ URL: https://github.com/pydantic/pydantic-core
Source: %{pypi_source pydantic_core}
# Manually created patch for downstream crate metadata changes
-# * Allow jiter 0.15 through 0.18. API changes from 0.14 to 0.17 are purely
-# additive, plus switching to PyO3 0.29, which we are also doing here, so
-# this is compatible. 0.18 switches to PyO3 0.30, but we patched it to
-# maintain 0.29 support for now. Downstream-only because jiter is developed
-# by the Pydantic people, and we can reasonably assume that they will update
-# in due course without prompting from us.
+# * Allow jiter 0.15 through 0.19. API changes from 0.14 to 0.17,
+# https://github.com/pydantic/pydantic/pull/13806, are purely additive, plus
+# switching to PyO3 0.29, which we are also doing here, so this is
+# compatible. 0.18, https://github.com/pydantic/pydantic/pull/14003, switches
+# to PyO3 0.30, but we patched it to maintain 0.29 support for now.
+# For 0.19, https://github.com/pydantic/pydantic/pull/14247.
# * Update lru to 0.18.2 for RUSTSEC-2026-0253:
# https://github.com/pydantic/pydantic/commit/97929719f013de7fcebf887e253d3021b8a1c3ea
# * Update to PyO3 0.29: https://github.com/pydantic/pydantic/pull/13301; this
reply other threads:[~2026-11-07 8:22 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=179403976108.1.3677025605058335629.rpms-python-pydantic-core-f35b5da76e3c@fedoraproject.org \
--to=code@musicinmybrain.net \
--cc=git-commits@fedoraproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox