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-uv-build] f44: Update to 0.11.28 (close RHBZ#2497949)
Date: Fri, 10 Jul 2026 08:27:31 GMT	[thread overview]
Message-ID: <178367205147.1.17596430494709988340.rpms-python-uv-build-9999ce6d8cb7@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/python-uv-build
Branch : f44
Commit : 9999ce6d8cb75f0b6864397b389e4934341d8cc7
Author : Benjamin A. Beasley <code@musicinmybrain.net>
Date   : 2026-07-08T09:58:03+01:00
Stats  : +3/-2 in 3 file(s)
URL    : https://src.fedoraproject.org/rpms/python-uv-build/c/9999ce6d8cb75f0b6864397b389e4934341d8cc7?branch=f44

Log:
Update to 0.11.28 (close RHBZ#2497949)

---
diff --git a/.gitignore b/.gitignore
index 008b9f5..cad4a32 100644
--- a/.gitignore
+++ b/.gitignore
@@ -119,3 +119,4 @@
 /uv_build-0.11.25.tar.gz
 /uv_build-0.11.26.tar.gz
 /uv_build-0.11.27.tar.gz
+/uv_build-0.11.28.tar.gz

diff --git a/python-uv-build.spec b/python-uv-build.spec
index c676058..8c42320 100644
--- a/python-uv-build.spec
+++ b/python-uv-build.spec
@@ -1,7 +1,7 @@
 %bcond check 1
 
 Name:           python-uv-build
-Version:        0.11.27
+Version:        0.11.28
 Release:        %autorelease
 Summary:        The uv build backend
 

diff --git a/sources b/sources
index 88a71e1..c340cb2 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (uv_build-0.11.27.tar.gz) = e7a7f461cf1ae899b24fcedc08fd739f352347eacb1f215026745a6b170e552504ed712b91519cff170ae81e36d6b7403a0270e9766e2cdf644411b51e62cf9c
+SHA512 (uv_build-0.11.28.tar.gz) = c502494cde643e2a5e45e34ba3be3132720f6ec4c7e4c966c02a673308d44f1ee313d84ab267ffb6cb88cb0227075b88369381bbe89b9b6333b1f4eb89bc0724

                 reply	other threads:[~2026-07-10  8:27 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=178367205147.1.17596430494709988340.rpms-python-uv-build-9999ce6d8cb7@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