public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Ali Erdinc Koroglu <ali.koroglu@oss.qualcomm.com>
To: git-commits@fedoraproject.org
Subject: [rpms/python-elastic-transport] rawhide: Update to 9.4.1
Date: Thu, 18 Jun 2026 16:46:16 GMT	[thread overview]
Message-ID: <178180117617.1.15677277519514657050.rpms-python-elastic-transport-e4cfd6950936@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/python-elastic-transport
Branch : rawhide
Commit : e4cfd695093654689fd1876c08824d85290084cf
Author : Ali Erdinc Koroglu <ali.koroglu@oss.qualcomm.com>
Date   : 2026-06-18T19:46:01+03:00
Stats  : +2/-2 in 2 file(s)
URL    : https://src.fedoraproject.org/rpms/python-elastic-transport/c/e4cfd695093654689fd1876c08824d85290084cf?branch=rawhide

Log:
Update to 9.4.1

---
diff --git a/python-elastic-transport.spec b/python-elastic-transport.spec
index d0ce6c4..5e5efd8 100644
--- a/python-elastic-transport.spec
+++ b/python-elastic-transport.spec
@@ -6,7 +6,7 @@ This library was lifted from elasticsearch-py and then transformed to be used
 across all Elastic services rather than only Elasticsearch.}
 
 Name:		python-%{srcname}
-Version:	9.1.0
+Version:	9.4.1
 Release:	%autorelease
 Summary:	Transport classes and utilities shared among Python Elastic
 

diff --git a/sources b/sources
index 4698a28..28336c6 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (elastic-transport-9.1.0.tar.gz) = 70a7301376d8e19d3d29d118a46efe52c74bb32758572eaf007cb6018363294c3c559298c54f0a483907daac0ff8ab60fd9e5704088658d5f4955922cb998615
+SHA512 (elastic-transport-9.4.1.tar.gz) = f7aa92bad0455d82de01329905bd561b3a3159d5cb711df9dd962f16f4a45557d486b38128c190dfe27e9f073592cb650e3ecd6165c4330f5c0e5b07922d9c8e

                 reply	other threads:[~2026-06-18 16:46 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=178180117617.1.15677277519514657050.rpms-python-elastic-transport-e4cfd6950936@fedoraproject.org \
    --to=ali.koroglu@oss.qualcomm.com \
    --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