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.6 (close RHBZ#2456895)
Date: Sun, 16 Aug 2026 07:55:50 GMT	[thread overview]
Message-ID: <178686695078.1.14554815164671397722.rpms-python-uv-build-3bde208be6e0@fedoraproject.org> (raw)

A new commit has been pushed.

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

Log:
Update to 0.11.6 (close RHBZ#2456895)

---
diff --git a/.gitignore b/.gitignore
index 32b46eb..a7042e0 100644
--- a/.gitignore
+++ b/.gitignore
@@ -101,3 +101,4 @@
 /uv_build-0.11.2.tar.gz
 /uv_build-0.11.4.tar.gz
 /uv_build-0.11.5.tar.gz
+/uv_build-0.11.6.tar.gz

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

diff --git a/sources b/sources
index 0cd518c..2c13a68 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (uv_build-0.11.5.tar.gz) = 731cdd7a17ba40d20add0ef9928c688016b4f19b5378a7cb71a3d02aca09a4585a1bd6b6304ef4c1b5745fe3edb5ee36a1a49b563946dd29d1e210fd5946d1de
+SHA512 (uv_build-0.11.6.tar.gz) = 8a9fc7cca9e42f42db888b6a9f3888393feae79d0ce8ca56568c83cbee977675d8a39a38b820606d1ac685ef99b92a182795c2521f4796865acd774fd73c6bac

                 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=178686695078.1.14554815164671397722.rpms-python-uv-build-3bde208be6e0@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