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.9 (close RHBZ#2466653)
Date: Sun, 16 Aug 2026 07:55:51 GMT	[thread overview]
Message-ID: <178686695168.1.16885572821727452301.rpms-python-uv-build-0f0fa0ef7430@fedoraproject.org> (raw)

A new commit has been pushed.

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

Log:
Update to 0.11.9 (close RHBZ#2466653)

---
diff --git a/.gitignore b/.gitignore
index 5404ba9..576f90d 100644
--- a/.gitignore
+++ b/.gitignore
@@ -103,3 +103,4 @@
 /uv_build-0.11.5.tar.gz
 /uv_build-0.11.6.tar.gz
 /uv_build-0.11.7.tar.gz
+/uv_build-0.11.9.tar.gz

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

diff --git a/sources b/sources
index 882fc11..d628601 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (uv_build-0.11.7.tar.gz) = 5ef23796480d36b20d1ca1b5c22eeb86c6634acbe9eb62642044d6c34a8dc45ca59727a77793fa324dbc3656a3659521544387d8afa346879675ff09fef1ca62
+SHA512 (uv_build-0.11.9.tar.gz) = 295758c60884c1f7a7ecafbfe368275497874f5f023164346143152674bab655548ca7c1389ca62a3db05f362bbf19cf686ffffad8bbaded017ed45cd22cc8a8

                 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=178686695168.1.16885572821727452301.rpms-python-uv-build-0f0fa0ef7430@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