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] f45: Update to 0.12.7
Date: Fri, 04 Sep 2026 06:03:21 GMT [thread overview]
Message-ID: <178850180102.1.6197439806485451146.rpms-python-uv-build-28b0ed7b947c@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/python-uv-build
Branch : f45
Commit : 28b0ed7b947c52bba37ebb3c764f1c48bf1dadfe
Author : Benjamin A. Beasley <code@musicinmybrain.net>
Date : 2026-09-02T23:15:20+01:00
Stats : +2/-9 in 2 file(s)
URL : https://src.fedoraproject.org/rpms/python-uv-build/c/28b0ed7b947c52bba37ebb3c764f1c48bf1dadfe?branch=f45
Log:
Update to 0.12.7
---
diff --git a/python-uv-build.spec b/python-uv-build.spec
index 063de30..f311ea1 100644
--- a/python-uv-build.spec
+++ b/python-uv-build.spec
@@ -1,7 +1,7 @@
%bcond check 1
Name: python-uv-build
-Version: 0.12.6
+Version: 0.12.7
Release: %autorelease
Summary: The uv build backend
@@ -142,13 +142,6 @@ tomcli set Cargo.toml false profile.release.strip
# # https://bugzilla.redhat.com/show_bug.cgi?id=1234567
# tomcli set Cargo.toml str workspace.dependencies.foocrate.version 0.1.2
-# tar-codec
-# wanted: 0.0.13
-# currently packaged: 0.0.14
-# A subsequent uv release will want the newer version, and it’s
-# backwards-compatible enough in practice.
-tomcli set Cargo.toml str workspace.dependencies.tar-codec.version 0.0.14
-
%cargo_prep
diff --git a/sources b/sources
index 44b400b..3dd2e00 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (uv_build-0.12.6.tar.gz) = c609f89b8c0f1decdf64c056084354ae04d6337e27dbd22297b5d462fcba0f0ce29f5a0a40b8f274ac5668f4805d9971b1da5509d10071ee2354f6fe78cc65ee
+SHA512 (uv_build-0.12.7.tar.gz) = 135f845b3ee6d1925f740917f83f94ec1a7e95aab5ed2db0aa70516c712ab0a143a0e427d3c172fac0bb1fabaa9103718bb2a26c31c9a287e3af65ac0175a245
reply other threads:[~2026-09-04 6:03 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=178850180102.1.6197439806485451146.rpms-python-uv-build-28b0ed7b947c@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