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] f44: Update to 0.11.18 (close RHBZ#2482964)
Date: Wed, 03 Jun 2026 18:10:09 GMT	[thread overview]
Message-ID: <178051020931.1.1117663178323483880.rpms-python-uv-build-73ef546d59a6@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/python-uv-build
Branch : f44
Commit : 73ef546d59a644b51570be1da5145114a2b8c43f
Author : Benjamin A. Beasley <code@musicinmybrain.net>
Date   : 2026-06-03T14:48:19+01:00
Stats  : +3/-2 in 3 file(s)
URL    : https://src.fedoraproject.org/rpms/python-uv-build/c/73ef546d59a644b51570be1da5145114a2b8c43f?branch=f44

Log:
Update to 0.11.18 (close RHBZ#2482964)

---
diff --git a/.gitignore b/.gitignore
index 7c635f6..947bc18 100644
--- a/.gitignore
+++ b/.gitignore
@@ -110,3 +110,4 @@
 /uv_build-0.11.14.tar.gz
 /uv_build-0.11.15.tar.gz
 /uv_build-0.11.16.tar.gz
+/uv_build-0.11.18.tar.gz

diff --git a/python-uv-build.spec b/python-uv-build.spec
index 73d3a18..b595088 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.16
+Version:        0.11.18
 Release:        %autorelease
 Summary:        The uv build backend
 

diff --git a/sources b/sources
index f54ab6a..d525535 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (uv_build-0.11.16.tar.gz) = fcc8bdf72e6d1769bc37668e8cbb3f8444f05ce3cb6eca6f949ec02d4adbe638b8f89b143a8af445c7c55ea5f9cffe1ea796ee49a6fdc1f60a07e9642cf9bd4e
+SHA512 (uv_build-0.11.18.tar.gz) = 87b7e5bc3e908f3dbd4ab5a9cca29b54a72c961ec15a2955586f9248742f79b6c0974200366ab831cba2be7393a273e9c0302323f7b7389960197194517edfe5

                 reply	other threads:[~2026-06-03 18:10 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=178051020931.1.1117663178323483880.rpms-python-uv-build-73ef546d59a6@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