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] epel10: Update to 0.9.22 (close RHBZ#2427389)
Date: Sun, 16 Aug 2026 07:55:39 GMT	[thread overview]
Message-ID: <178686693963.1.12132357125543540797.rpms-python-uv-build-2c1c0fbc914a@fedoraproject.org> (raw)

A new commit has been pushed.

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

Log:
Update to 0.9.22 (close RHBZ#2427389)

---
diff --git a/.gitignore b/.gitignore
index bf1c340..10475fc 100644
--- a/.gitignore
+++ b/.gitignore
@@ -79,3 +79,4 @@
 /uv_build-0.9.18.tar.gz
 /uv_build-0.9.20.tar.gz
 /uv_build-0.9.21.tar.gz
+/uv_build-0.9.22.tar.gz

diff --git a/python-uv-build.spec b/python-uv-build.spec
index 71e7ccd..8e39fa0 100644
--- a/python-uv-build.spec
+++ b/python-uv-build.spec
@@ -1,7 +1,7 @@
 %bcond check 1
 
 Name:           python-uv-build
-Version:        0.9.21
+Version:        0.9.22
 Release:        %autorelease
 Summary:        The uv build backend
 

diff --git a/sources b/sources
index 662eea9..84aea3d 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (uv_build-0.9.21.tar.gz) = 1e2885f978fa45e1481a72a35d5734ef80d3ab7da0213fc41cad8c4e49756bf0b172cea570d25a6b0461c6dd13fead8a8fae356b11ec758f8bd7b915faa322c4
+SHA512 (uv_build-0.9.22.tar.gz) = dbb19e42fae9ba49eae7a5e55395b4c04542142a22a421ced43195eb616eeec53126452b1f716e9d4cb8a528adf54ab72ab1f36236e5ea1a7a0e7da8d28cf36a

                 reply	other threads:[~2026-08-16  7:55 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=178686693963.1.12132357125543540797.rpms-python-uv-build-2c1c0fbc914a@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