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.9.29 (close RHBZ#2436549)
Date: Sun, 16 Aug 2026 07:55:42 GMT	[thread overview]
Message-ID: <178686694212.1.16915473237003828951.rpms-python-uv-build-1954aa315bbb@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/python-uv-build
Branch : epel10
Commit : 1954aa315bbb2476a8fb3f09e602e057a0138fd5
Author : Benjamin A. Beasley <code@musicinmybrain.net>
Date   : 2026-02-03T22:43:02+00:00
Stats  : +3/-2 in 3 file(s)
URL    : https://src.fedoraproject.org/rpms/python-uv-build/c/1954aa315bbb2476a8fb3f09e602e057a0138fd5?branch=epel10

Log:
Update to 0.9.29 (close RHBZ#2436549)

---
diff --git a/.gitignore b/.gitignore
index bbcbc13..8ac47b3 100644
--- a/.gitignore
+++ b/.gitignore
@@ -83,3 +83,4 @@
 /uv_build-0.9.26.tar.gz
 /uv_build-0.9.27.tar.gz
 /uv_build-0.9.28.tar.gz
+/uv_build-0.9.29.tar.gz

diff --git a/python-uv-build.spec b/python-uv-build.spec
index ffad5ea..768e35a 100644
--- a/python-uv-build.spec
+++ b/python-uv-build.spec
@@ -1,7 +1,7 @@
 %bcond check 1
 
 Name:           python-uv-build
-Version:        0.9.28
+Version:        0.9.29
 Release:        %autorelease
 Summary:        The uv build backend
 

diff --git a/sources b/sources
index e508ca4..6465625 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (uv_build-0.9.28.tar.gz) = d12d6850f231535f9f6a4abb2086eee76f527fe396b9e5cb63abf6697353c07e8e24c9479804cdcec64054230fea751525d24ce05c811a8d02e03acc5c96957c
+SHA512 (uv_build-0.9.29.tar.gz) = ad449f2dcc4b0132f9610124a0ab66145c9f53e81ade24694b4c83f41a0922e6ec1e993898b1c94d2eb872bf8df6313105e6f7d395dbd8f63a6476d199f4f6bb

                 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=178686694212.1.16915473237003828951.rpms-python-uv-build-1954aa315bbb@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