public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Packit <hello@packit.dev>
To: git-commits@fedoraproject.org
Subject: [rpms/packit] epel10: Update to 1.16.1 upstream release
Date: Mon, 15 Jun 2026 06:40:56 GMT [thread overview]
Message-ID: <178150565660.1.1312450247061494173.rpms-packit-6359079f7da5@fedoraproject.org> (raw)
A new commit has been pushed.
Repo : rpms/packit
Branch : epel10
Commit : 6359079f7da5a1abd6faa0204090cf67116b2667
Author : Packit <hello@packit.dev>
Date : 2026-06-14T18:07:40+00:00
Stats : +9/-4 in 5 file(s)
URL : https://src.fedoraproject.org/rpms/packit/c/6359079f7da5a1abd6faa0204090cf67116b2667?branch=epel10
Log:
Update to 1.16.1 upstream release
- Resolves: rhbz#2488767
Upstream tag: 1.16.1
Upstream commit: 6e09edce
Commit authored by Packit automation (https://packit.dev/)
---
diff --git a/.gitignore b/.gitignore
index 8e6c027..893b840 100644
--- a/.gitignore
+++ b/.gitignore
@@ -3,3 +3,4 @@
/packitos-1.15.2.tar.gz
/packitos-1.15.3.tar.gz
/packitos-1.16.0.tar.gz
+/packitos-1.16.1.tar.gz
diff --git a/README.packit b/README.packit
index 7698114..4e76cbe 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.15.3.post1.dev4+g553394da5.
+The file was generated using packit 1.16.0.post1.dev8+g8a0482385.
diff --git a/packit.spec b/packit.spec
index d7af6a4..b33d546 100644
--- a/packit.spec
+++ b/packit.spec
@@ -6,7 +6,7 @@
%endif
Name: packit
-Version: 1.16.0
+Version: 1.16.1
Release: 1%{?dist}
Summary: A tool for integrating upstream projects with Fedora operating system
@@ -78,6 +78,10 @@ cp files/bash-completion/packit %{buildroot}%{bash_completions_dir}/packit
%doc README.md
%changelog
+* Sun Jun 14 2026 Packit <hello@packit.dev> - 1.16.1-1
+- Fixed a couple of Copr-related issues. (#2721, #2727)
+- Resolves: rhbz#2488767
+
* Fri Apr 24 2026 Packit <hello@packit.dev> - 1.16.0-1
- Packit CLI has a new option `--[no-]update-release` that, by default, follows the value of the option set in the config, and also allows you to override manually, if necessary. (#2713)
- In addition to `version_update_mask`, users can now use a new `version_update_specifiers` configuration option to control the upstream versions allowed to be release-synced. The option accepts [PEP440 version specifier sets](https://packaging.pypa.io/en/stable/specifiers.html), for example `version_update_specifiers: >=1.0,~=1.0`. (#2710)
diff --git a/plans/main.fmf b/plans/main.fmf
index 4cfa456..a4b19ec 100644
--- a/plans/main.fmf
+++ b/plans/main.fmf
@@ -1,6 +1,6 @@
discover:
how: fmf
url: https://github.com/packit/packit.git
- ref: 3824aae58b21d6a38bbcb49a9fe53484143a4569
+ ref: 6e09edce1afd9c96955ef4ddb4da3a206c658f69
execute:
how: tmt
diff --git a/sources b/sources
index 7f39d0e..248ce43 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (packitos-1.16.0.tar.gz) = cb9edfa23a5153439739f13e82da13e3017d97f43d2fdfdf8c1afd6e7de7b31f64c29c006c5f0dbda353fa4a12f1a7761935353ef87b306f71d109abf09bc802
+SHA512 (packitos-1.16.1.tar.gz) = 6a8ef7f836c013b5c4c38568f97f7d9ce4db805c7b9bfb5db78c0fdd902677b496b7630005e6884cfb30fdda70cc8f7a165e6da0c314fc07e21788771bb97aff
reply other threads:[~2026-06-15 6:40 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=178150565660.1.1312450247061494173.rpms-packit-6359079f7da5@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