public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Packit <hello@packit.dev>
To: git-commits@fedoraproject.org
Subject: [rpms/skopeo] rawhide: Update to 1.24.0 upstream release
Date: Thu, 30 Jul 2026 19:31:38 GMT	[thread overview]
Message-ID: <178543989808.1.6036153809571317096.rpms-skopeo-edcf2b6eeb6f@fedoraproject.org> (raw)

            A new commit has been pushed.

            Repo   : rpms/skopeo
            Branch : rawhide
            Commit : edcf2b6eeb6f5e8882a048e7378b7e327cc3a52f
            Author : Packit <hello@packit.dev>
            Date   : 2026-07-30T18:23:33+00:00
            Stats  : +6/-5 in 6 file(s)
            URL    : https://src.fedoraproject.org/rpms/skopeo/c/edcf2b6eeb6f5e8882a048e7378b7e327cc3a52f?branch=rawhide

            Log:
            Update to 1.24.0 upstream release

Upstream tag: v1.24.0
Upstream commit: ea7faa7b

Commit authored by Packit automation (https://packit.dev/)

---
diff --git a/.gitignore b/.gitignore
index 389269d..ea6d4f9 100644
--- a/.gitignore
+++ b/.gitignore
@@ -328,3 +328,4 @@
 /v1.22.1.tar.gz
 /v1.22.2.tar.gz
 /v1.23.0.tar.gz
+/v1.24.0.tar.gz

diff --git a/.packit.yaml b/.packit.yaml
index 82fcf8c..29d4a85 100644
--- a/.packit.yaml
+++ b/.packit.yaml
@@ -4,7 +4,7 @@
 
 # NOTE: The Packit copr_build tasks help to check if every commit builds on
 # supported Fedora and CentOS Stream arches.
-# They do not block the current Cirrus-based workflow.
+# They do not block the GitHub Actions PR workflow.
 
 downstream_package_name: skopeo
 upstream_tag_template: v{version}

diff --git a/README.packit b/README.packit
index ead62b8..d816803 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.16.0.post1.dev6+g4581d2cd8.
+The file was generated using packit 1.16.2.

diff --git a/plans/main.fmf b/plans/main.fmf
index adc46f2..71b8a45 100644
--- a/plans/main.fmf
+++ b/plans/main.fmf
@@ -1,7 +1,7 @@
 discover:
     how: fmf
     url: https://github.com/containers/skopeo
-    ref: v1.23.0
+    ref: v1.24.0
 execute:
     how: tmt
 prepare:

diff --git a/skopeo.spec b/skopeo.spec
index 4460154..50e998b 100644
--- a/skopeo.spec
+++ b/skopeo.spec
@@ -40,7 +40,7 @@ Epoch: %{conditional_epoch}
 # If that's what you're reading, Version must be 0, and will be updated by Packit for
 # copr and koji builds.
 # If you're reading this on dist-git, the version is automatically filled in by Packit.
-Version: 1.23.0
+Version: 1.24.0
 # The `AND` needs to be uppercase in the License for SPDX compatibility
 License: Apache-2.0 AND BSD-2-Clause AND BSD-3-Clause AND ISC AND MIT AND MPL-2.0
 Release: %autorelease

diff --git a/sources b/sources
index bd1c9cc..dc7de31 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (v1.23.0.tar.gz) = 0985ac478b27bace31f5f2710bae44d214b90f160e61400d6d345e728779389103a3b9c4bcfd048f0d7d12d4dc7dcd8e0b2e20b1a8c18bdef652faa153fe0726
+SHA512 (v1.24.0.tar.gz) = 5c4ba7d1f4a86546fedd8aab0b69139e9376a158b62b1876aff695c65cd2d16bf7380bdf2d3d3ae691582bb2a8acb837d0f6f517161d3c95945995a57bc112d2

                 reply	other threads:[~2026-07-30 19:31 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=178543989808.1.6036153809571317096.rpms-skopeo-edcf2b6eeb6f@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