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] f43: Update to 0.11.21 (close RHBZ#2487855)
Date: Wed, 17 Jun 2026 12:51:17 GMT	[thread overview]
Message-ID: <178170067784.1.7448815755014136599.rpms-python-uv-build-a7a475e8e49b@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/python-uv-build
Branch : f43
Commit : a7a475e8e49b0dce8b7676ceea2e028cc22df13d
Author : Benjamin A. Beasley <code@musicinmybrain.net>
Date   : 2026-06-13T06:12:27+01:00
Stats  : +3/-2 in 3 file(s)
URL    : https://src.fedoraproject.org/rpms/python-uv-build/c/a7a475e8e49b0dce8b7676ceea2e028cc22df13d?branch=f43

Log:
Update to 0.11.21 (close RHBZ#2487855)

---
diff --git a/.gitignore b/.gitignore
index e4afd9b..a3b35a0 100644
--- a/.gitignore
+++ b/.gitignore
@@ -112,3 +112,4 @@
 /uv_build-0.11.16.tar.gz
 /uv_build-0.11.18.tar.gz
 /uv_build-0.11.19.tar.gz
+/uv_build-0.11.21.tar.gz

diff --git a/python-uv-build.spec b/python-uv-build.spec
index d42e849..1400ae7 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.19
+Version:        0.11.21
 Release:        %autorelease
 Summary:        The uv build backend
 

diff --git a/sources b/sources
index a032335..637e6de 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (uv_build-0.11.19.tar.gz) = 9ff1f62933f1f3a81386306ad64c65153848ff9461ee6b690455d1bf6f41ac2287302e42afe11dbc9b1532c08908f96d5158d5b2ff0e829a10330472b7f346cc
+SHA512 (uv_build-0.11.21.tar.gz) = 7ee8b981791533f35313afde228b38de5dd460713a9453b61f620df63f5a6feb0cb2cd18e2a3fb29199e13a9781f31bf850002f9b4a747c14e3cf0579f8ba970

                 reply	other threads:[~2026-06-17 12:51 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=178170067784.1.7448815755014136599.rpms-python-uv-build-a7a475e8e49b@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