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.7.2
Date: Sun, 16 Aug 2026 07:55:02 GMT [thread overview]
Message-ID: <178686690252.1.7014869040027846393.rpms-python-uv-build-d4fc61960ed0@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/python-uv-build
Branch : epel10
Commit : d4fc61960ed08a89b4c0dec6cc44231729f2a2e2
Author : Benjamin A. Beasley <code@musicinmybrain.net>
Date : 2025-05-09T19:33:46-04:00
Stats : +3/-2 in 3 file(s)
URL : https://src.fedoraproject.org/rpms/python-uv-build/c/d4fc61960ed08a89b4c0dec6cc44231729f2a2e2?branch=epel10
Log:
Update to 0.7.2
---
diff --git a/.gitignore b/.gitignore
index 69e6d9d..3a43703 100644
--- a/.gitignore
+++ b/.gitignore
@@ -7,3 +7,4 @@
/pubgrub-a3b4db3abb1829ce889fb89fa6d157fef529ef7e.tar.gz
/uv_build-0.7.0.tar.gz
/uv_build-0.7.1.tar.gz
+/uv_build-0.7.2.tar.gz
diff --git a/python-uv-build.spec b/python-uv-build.spec
index fcfd454..f65c390 100644
--- a/python-uv-build.spec
+++ b/python-uv-build.spec
@@ -1,7 +1,7 @@
%bcond check 1
Name: python-uv-build
-Version: 0.7.1
+Version: 0.7.2
Release: %autorelease
Summary: The uv build backend
diff --git a/sources b/sources
index 9d10259..f879f50 100644
--- a/sources
+++ b/sources
@@ -1,2 +1,2 @@
-SHA512 (uv_build-0.7.1.tar.gz) = 5c68dc4f62d9a6d976ddc3e474f5403c9d5d54d87f9bba76c1f0f005d5d73d7e221b8c758e02ab322b614c265d2d9da4e9ec46589d91738ae5d9f0ad0514dfe8
+SHA512 (uv_build-0.7.2.tar.gz) = db0f3b31148e0695f3f16b51f97ae781451c59fbd9ee7049a410ac5d5f9cdbe35215ae5b0682ec81d5d3a3bf8c963864c2b678098ba7522f58e87f346bd5746e
SHA512 (pubgrub-a3b4db3abb1829ce889fb89fa6d157fef529ef7e.tar.gz) = 3e434326040445b836bbbb5e3af186a480198cae3d9b3bc78fa1e8c7f78b558ef15de88c6c941d25ada6be80ca7bb5cf1e1c10647b3e991aeb44cb58acccff35
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=178686690252.1.7014869040027846393.rpms-python-uv-build-d4fc61960ed0@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