public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Andrew Bauer <zonexpertconsulting@outlook.com>
To: git-commits@fedoraproject.org
Subject: [rpms/perl-Schedule-Cron] f44: 1.06 release
Date: Mon, 20 Jul 2026 21:14:55 GMT [thread overview]
Message-ID: <178458209595.1.6846985274965371840.rpms-perl-Schedule-Cron-27543344d91a@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/perl-Schedule-Cron
Branch : f44
Commit : 27543344d91a91c669b2a8b92bf64ebcd1b2e542
Author : Andrew Bauer <zonexpertconsulting@outlook.com>
Date : 2026-07-20T16:14:02-05:00
Stats : +7/-3 in 3 file(s)
URL : https://src.fedoraproject.org/rpms/perl-Schedule-Cron/c/27543344d91a91c669b2a8b92bf64ebcd1b2e542?branch=f44
Log:
1.06 release
---
diff --git a/.gitignore b/.gitignore
index eb1a7a9..b5d80e1 100644
--- a/.gitignore
+++ b/.gitignore
@@ -2,3 +2,4 @@
/Schedule-Cron-1.03.tar.gz
/Schedule-Cron-1.04.tar.gz
/Schedule-Cron-1.05.tar.gz
+/Schedule-Cron-1.06.tar.gz
diff --git a/perl-Schedule-Cron.spec b/perl-Schedule-Cron.spec
index 211661b..58e1fb3 100644
--- a/perl-Schedule-Cron.spec
+++ b/perl-Schedule-Cron.spec
@@ -2,8 +2,8 @@
Name: perl-Schedule-Cron
Summary: Provides a simple but complete cron like scheduler
-Version: 1.05
-Release: 10%{?dist}
+Version: 1.06
+Release: 1%{?dist}
# Automatically converted from old format: GPL+ or Artistic - review is highly recommended.
License: GPL-1.0-or-later OR Artistic-1.0-Perl
URL: https://metacpan.org/release/Schedule-Cron
@@ -89,6 +89,9 @@ find %{buildroot} -type f -name .packlist -delete
%{_mandir}/man3/*
%changelog
+* Mon Jul 20 2026 Andrew Bauer <zonexpertconsulting@outlook.com> - 1.06-1
+- 1.06 release
+
* Thu Jul 16 2026 Fedora Release Engineering <releng@fedoraproject.org> - 1.05-10
- Rebuilt for https://fedoraproject.org/wiki/Fedora_45_Mass_Rebuild
diff --git a/sources b/sources
index 49ef755..176a4d3 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (Schedule-Cron-1.05.tar.gz) = 0ae856833f867f84cb2fe553d03279e6b82312725f732cb537f189da99ac300da464c4cc53cd0d0961c6ba44e396ed18f07e868261fbf12db3ef19160bd8152b
+SHA512 (Schedule-Cron-1.06.tar.gz) = 8d947cf0550a31f27b2086b8d3ff2ea2f31fcc9794e5199c8f41d34a32ed700abd06eec22a6291f21e97b1170c10d290eaa406f9b69301d9f4daf846f3079094
reply other threads:[~2026-07-20 21:14 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=178458209595.1.6846985274965371840.rpms-perl-Schedule-Cron-27543344d91a@fedoraproject.org \
--to=zonexpertconsulting@outlook.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