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.11.7 (close RHBZ#2458852)
Date: Sun, 16 Aug 2026 07:55:51 GMT	[thread overview]
Message-ID: <178686695127.1.16719467665716267613.rpms-python-uv-build-02246147e212@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/python-uv-build
Branch : epel10
Commit : 02246147e212cabcf6b5b3c7e437c02140d87dfa
Author : Benjamin A. Beasley <code@musicinmybrain.net>
Date   : 2026-04-16T11:37:07+01:00
Stats  : +3/-2 in 3 file(s)
URL    : https://src.fedoraproject.org/rpms/python-uv-build/c/02246147e212cabcf6b5b3c7e437c02140d87dfa?branch=epel10

Log:
Update to 0.11.7 (close RHBZ#2458852)

---
diff --git a/.gitignore b/.gitignore
index a7042e0..5404ba9 100644
--- a/.gitignore
+++ b/.gitignore
@@ -102,3 +102,4 @@
 /uv_build-0.11.4.tar.gz
 /uv_build-0.11.5.tar.gz
 /uv_build-0.11.6.tar.gz
+/uv_build-0.11.7.tar.gz

diff --git a/python-uv-build.spec b/python-uv-build.spec
index 450cd77..ebd5e39 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.6
+Version:        0.11.7
 Release:        %autorelease
 Summary:        The uv build backend
 

diff --git a/sources b/sources
index 2c13a68..882fc11 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (uv_build-0.11.6.tar.gz) = 8a9fc7cca9e42f42db888b6a9f3888393feae79d0ce8ca56568c83cbee977675d8a39a38b820606d1ac685ef99b92a182795c2521f4796865acd774fd73c6bac
+SHA512 (uv_build-0.11.7.tar.gz) = 5ef23796480d36b20d1ca1b5c22eeb86c6634acbe9eb62642044d6c34a8dc45ca59727a77793fa324dbc3656a3659521544387d8afa346879675ff09fef1ca62

                 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=178686695127.1.16719467665716267613.rpms-python-uv-build-02246147e212@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