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.30 (close RHBZ#2436958)
Date: Sun, 16 Aug 2026 07:55:42 GMT	[thread overview]
Message-ID: <178686694261.1.17299715437226038741.rpms-python-uv-build-fde17f932651@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/python-uv-build
Branch : epel10
Commit : fde17f9326518f0d47c412f6e26a34573d1eb4ea
Author : Benjamin A. Beasley <code@musicinmybrain.net>
Date   : 2026-02-05T06:57:55+00:00
Stats  : +3/-2 in 3 file(s)
URL    : https://src.fedoraproject.org/rpms/python-uv-build/c/fde17f9326518f0d47c412f6e26a34573d1eb4ea?branch=epel10

Log:
Update to 0.9.30 (close RHBZ#2436958)

---
diff --git a/.gitignore b/.gitignore
index 8ac47b3..a1daed6 100644
--- a/.gitignore
+++ b/.gitignore
@@ -84,3 +84,4 @@
 /uv_build-0.9.27.tar.gz
 /uv_build-0.9.28.tar.gz
 /uv_build-0.9.29.tar.gz
+/uv_build-0.9.30.tar.gz

diff --git a/python-uv-build.spec b/python-uv-build.spec
index 768e35a..0c5e3c0 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.29
+Version:        0.9.30
 Release:        %autorelease
 Summary:        The uv build backend
 

diff --git a/sources b/sources
index 6465625..170040e 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (uv_build-0.9.29.tar.gz) = ad449f2dcc4b0132f9610124a0ab66145c9f53e81ade24694b4c83f41a0922e6ec1e993898b1c94d2eb872bf8df6313105e6f7d395dbd8f63a6476d199f4f6bb
+SHA512 (uv_build-0.9.30.tar.gz) = 378abd79176fd944c5d34da3de9ff55a1413a6961b1cbf9b45c05fd7eba55258643b0ff9e5dbf993af91e9dd52749cd895b4d0c7c0fe0bb75835361f362ca204

                 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=178686694261.1.17299715437226038741.rpms-python-uv-build-fde17f932651@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