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] f43: Update to 0.11.32 (close RHBZ#2506656)
Date: Fri, 24 Jul 2026 07:16:48 GMT	[thread overview]
Message-ID: <178487740899.1.1242413792104124739.rpms-python-uv-build-99c6cf18b70b@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/python-uv-build
Branch : f43
Commit : 99c6cf18b70b76084472d7c4f6ab98b8058e8dcf
Author : Benjamin A. Beasley <code@musicinmybrain.net>
Date   : 2026-07-24T06:51:39+01:00
Stats  : +3/-2 in 3 file(s)
URL    : https://src.fedoraproject.org/rpms/python-uv-build/c/99c6cf18b70b76084472d7c4f6ab98b8058e8dcf?branch=f43

Log:
Update to 0.11.32 (close RHBZ#2506656)

---
diff --git a/.gitignore b/.gitignore
index 7ef4527..c7db9ca 100644
--- a/.gitignore
+++ b/.gitignore
@@ -121,3 +121,4 @@
 /uv_build-0.11.27.tar.gz
 /uv_build-0.11.28.tar.gz
 /uv_build-0.11.31.tar.gz
+/uv_build-0.11.32.tar.gz

diff --git a/python-uv-build.spec b/python-uv-build.spec
index ba2ed5a..2faf964 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.31
+Version:        0.11.32
 Release:        %autorelease
 Summary:        The uv build backend
 

diff --git a/sources b/sources
index ba4c436..7aa94ca 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (uv_build-0.11.31.tar.gz) = e4b58173395c1da961ad5ec6c9b8862646c2fc71b902c3e3cb3507ca5a915617b29c794008b10cb8b796fb0f6a13420f730e0640576f7deeac22e832204abee2
+SHA512 (uv_build-0.11.32.tar.gz) = 3732f141b2ffeaed8f08dadadb2b5e72c2d60e0cb9a13c7d6b7360471606afbaae88d841db655b79ca2753ef4e2e18dbb51464e6669c57aed98ee19219fa5b56

                 reply	other threads:[~2026-07-24  7:16 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=178487740899.1.1242413792104124739.rpms-python-uv-build-99c6cf18b70b@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