public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Packit <hello@packit.dev>
To: git-commits@fedoraproject.org
Subject: [rpms/bluechi] epel10: Update to 1.3.0 upstream release
Date: Mon, 24 Aug 2026 09:58:28 GMT [thread overview]
Message-ID: <178756550811.1.15085830035605812175.rpms-bluechi-f4fc7e24dfbd@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/bluechi
Branch : epel10
Commit : f4fc7e24dfbdcfd9cbf7d4a967a881304c5e4c44
Author : Packit <hello@packit.dev>
Date : 2026-08-24T08:38:53+00:00
Stats : +6/-22 in 4 file(s)
URL : https://src.fedoraproject.org/rpms/bluechi/c/f4fc7e24dfbdcfd9cbf7d4a967a881304c5e4c44?branch=epel10
Log:
Update to 1.3.0 upstream release
Upstream tag: v1.3.0
Upstream commit: 71e85a72
Commit authored by Packit automation (https://packit.dev/)
---
diff --git a/.packit.yml b/.packit.yml
index c7f4aa8..6873dbd 100644
--- a/.packit.yml
+++ b/.packit.yml
@@ -35,12 +35,8 @@ jobs:
- job: copr_build
trigger: pull_request
targets:
- - epel-9-x86_64
- epel-10-x86_64
- fedora-rawhide-aarch64
- - fedora-rawhide-i386
- - fedora-rawhide-ppc64le
- - fedora-rawhide-s390x
- fedora-rawhide-x86_64
- &tests
@@ -88,26 +84,11 @@ jobs:
failure_comment:
message: "BlueChi build failed for merged commit {commit_sha}. Please check logs {logs_url}, packit dashboard {packit_dashboard_url} and external service dashboard {external_dashboard_url}"
targets:
- - centos-stream-9-aarch64
- - centos-stream-9-ppc64le
- - centos-stream-9-s390x
- - centos-stream-9-x86_64
- centos-stream-10-aarch64
- - centos-stream-10-ppc64le
- - centos-stream-10-s390x
- centos-stream-10-x86_64
- - epel-9-aarch64
- - epel-9-ppc64le
- - epel-9-s390x
- - epel-9-x86_64
- epel-10-aarch64
- - epel-10-ppc64le
- - epel-10-s390x
- epel-10-x86_64
- fedora-all-aarch64
- - fedora-all-i386
- - fedora-all-ppc64le
- - fedora-all-s390x
- fedora-all-x86_64
- job: propose_downstream
diff --git a/README.packit b/README.packit
index 46915dc..09d231a 100644
--- a/README.packit
+++ b/README.packit
@@ -1,3 +1,3 @@
This repository is maintained by packit.
https://packit.dev/
-The file was generated using packit 1.14.0.post1.dev6+g54773bdd6.
+The file was generated using packit 1.16.2.post1.dev12+g819bb7962.
diff --git a/bluechi.spec b/bluechi.spec
index 700ce8b..e247dca 100644
--- a/bluechi.spec
+++ b/bluechi.spec
@@ -10,7 +10,7 @@
Name: bluechi
-Version: 1.2.2
+Version: 1.3.0
Release: 1%{?dist}
Summary: A systemd service controller for multi-nodes environments
License: LGPL-2.1-or-later AND CC0-1.0
@@ -356,6 +356,9 @@ build-scripts/generate-unit-tests-code-coverage.sh %{_vpath_builddir} %{buildroo
%changelog
+* Mon Aug 24 2026 Packit <hello@packit.dev> - 1.3.0-1
+- Update to version 1.3.0
+
* Tue Feb 03 2026 Packit <hello@packit.dev> - 1.2.2-1
- Update to version 1.2.2
diff --git a/sources b/sources
index 83e19d9..081f2c0 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (bluechi-1.2.2.tar.gz) = 90c07d07cae8d987b533a2afcd95c3da346ca0a6b5919d98ba6c5334f7c7a59c2a7f274c94db231371d05f01e10a9dc5f837b8647f42d27273186a93ccb93b1d
+SHA512 (bluechi-1.3.0.tar.gz) = 9d1d0668d188b70a75429c29c2614a51cb795c402faf646fcbb7a69ebf213943cde1a99acd545eeedbea2ebd6cf7e607254a2f0d646f8cfb85363c3ec8128cd8
reply other threads:[~2026-08-24 9:58 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=178756550811.1.15085830035605812175.rpms-bluechi-f4fc7e24dfbd@fedoraproject.org \
--to=hello@packit.dev \
--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