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-openapi-core] rawhide: Allow all Starlette 1.x versions, avoiding upstream’s minor-version pin
Date: Wed, 03 Jun 2026 20:15:59 GMT [thread overview]
Message-ID: <178051775927.1.2538147391366663399.rpms-python-openapi-core-52efa0dfb507@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/python-openapi-core
Branch : rawhide
Commit : 52efa0dfb507bf42033a86c24f56bc6d51049fdd
Author : Benjamin A. Beasley <code@musicinmybrain.net>
Date : 2026-06-03T20:55:11+01:00
Stats : +4/-0 in 1 file(s)
URL : https://src.fedoraproject.org/rpms/python-openapi-core/c/52efa0dfb507bf42033a86c24f56bc6d51049fdd?branch=rawhide
Log:
Allow all Starlette 1.x versions, avoiding upstream’s minor-version pin
- Fixes RHBZ#2481164
---
diff --git a/python-openapi-core.spec b/python-openapi-core.spec
index f4ee32a..00759f4 100644
--- a/python-openapi-core.spec
+++ b/python-openapi-core.spec
@@ -54,6 +54,10 @@ sed -r -i '/^--cov[-=]/d' pyproject.toml
# We cannot respect a SemVer or version range pin on FastAPI; it updates
# frequently, with usually-tiny breaking changes.
%pyproject_patch_dependency fastapi:drop_upper
+# Now that Starlette is at 1.x, but upstream is still pinning particular minor
+# versions, it’s far too fussy to be constantly patching the version bounds.
+# Rather than dropping the upper bound entirely, loosen it to a SemVer bound.
+%pyproject_patch_dependency starlette:set_upper:2.0
# Erroring on DeprecationWarnings makes sense upstream, but is probably too
# strict for distribution packaging.
#
reply other threads:[~2026-06-03 20:15 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=178051775927.1.2538147391366663399.rpms-python-openapi-core-52efa0dfb507@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