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.13 (close RHBZ#2372600)
Date: Sun, 16 Aug 2026 07:55:08 GMT [thread overview]
Message-ID: <178686690804.1.9314780533349196857.rpms-python-uv-build-062d12883300@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/python-uv-build
Branch : epel10
Commit : 062d128833009cdd6a2c56615ed279806123d6b7
Author : Benjamin A. Beasley <code@musicinmybrain.net>
Date : 2025-06-13T05:08:18-04:00
Stats : +3/-2 in 3 file(s)
URL : https://src.fedoraproject.org/rpms/python-uv-build/c/062d128833009cdd6a2c56615ed279806123d6b7?branch=epel10
Log:
Update to 0.7.13 (close RHBZ#2372600)
---
diff --git a/.gitignore b/.gitignore
index bb17d3f..b2c36f3 100644
--- a/.gitignore
+++ b/.gitignore
@@ -19,3 +19,4 @@
/uv_build-0.7.10.tar.gz
/uv_build-0.7.11.tar.gz
/uv_build-0.7.12.tar.gz
+/uv_build-0.7.13.tar.gz
diff --git a/python-uv-build.spec b/python-uv-build.spec
index b3a244b..419cd3a 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.12
+Version: 0.7.13
Release: %autorelease
Summary: The uv build backend
diff --git a/sources b/sources
index 429c451..b67c525 100644
--- a/sources
+++ b/sources
@@ -1,2 +1,2 @@
-SHA512 (uv_build-0.7.12.tar.gz) = 8dd406e7369d7b8f9a318bbe7c1827588dc302862ae452b5233602fd0461eef52fe8a217b7f92075c19d55277ccb66b76f915ce7c2d58aefe062703e92a27932
+SHA512 (uv_build-0.7.13.tar.gz) = 44026e1139c95d082871a93d7d456684b07aa0b8f34609aabf1b7a74a81431a6811973e141cdc98c377b65e06b8ed56c6ca2393688132b6813363a00e622a911
SHA512 (pubgrub-06ec5a5f59ffaeb6cf5079c6cb184467da06c9db.tar.gz) = 3f0b18aecbc73fee91fc7de9f10d240ddc06c836fa2f116c1f007dd7818d099e6aea1852ca0b8d1a26ac19aac896535dba1a6298851a65515b553810c6245784
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=178686690804.1.9314780533349196857.rpms-python-uv-build-062d12883300@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