public inbox for git-commits@fedoraproject.org
help / color / mirror / Atom feed
From: Vojtech Polasek <vpolasek@redhat.com>
To: git-commits@fedoraproject.org
Subject: [rpms/scap-security-guide] rawhide: update to the latest upstream version 0.1.81
Date: Tue, 02 Jun 2026 12:49:24 GMT	[thread overview]
Message-ID: <178040456428.1.12382492620158495448.rpms-scap-security-guide-287b196c303a@fedoraproject.org> (raw)

A new commit has been pushed.

Repo   : rpms/scap-security-guide
Branch : rawhide
Commit : 287b196c303a73cd2f632d2048a782d342dcc18e
Author : Vojtech Polasek <vpolasek@redhat.com>
Date   : 2026-06-02T11:37:17+02:00
Stats  : +7/-3 in 3 file(s)
URL    : https://src.fedoraproject.org/rpms/scap-security-guide/c/287b196c303a73cd2f632d2048a782d342dcc18e?branch=rawhide

Log:
update to the latest upstream version 0.1.81

---
diff --git a/.gitignore b/.gitignore
index d0bbac5..d89dfc0 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1,3 +1,4 @@
 /scap-security-guide-0.1.78.tar.bz2
 /scap-security-guide-0.1.79.tar.bz2
 /scap-security-guide-0.1.80.tar.bz2
+/scap-security-guide-0.1.81.tar.bz2

diff --git a/scap-security-guide.spec b/scap-security-guide.spec
index 10800c4..02e9c2d 100644
--- a/scap-security-guide.spec
+++ b/scap-security-guide.spec
@@ -4,8 +4,8 @@
 %global _vpath_builddir build
 
 Name:		scap-security-guide
-Version:	0.1.80
-Release:	3%{?dist}
+Version:	0.1.81
+Release:	1%{?dist}
 Summary:	Security guidance and baselines in SCAP formats
 License:	BSD-3-Clause
 URL:		https://github.com/ComplianceAsCode/content/
@@ -96,6 +96,9 @@ rm %{buildroot}/%{_docdir}/%{name}/Contributors.md
 %endif
 
 %changelog
+* Tue Jun 02 2026 Vojtech Polasek <vpolasek@redhat.com> - 0.1.81-1
+- update to the latest upstream release 0.1.81
+
 * Fri Mar 27 2026 Vojtech Polasek <vpolasek@redhat.com> - 0.1.80-3
 - rebuilt to honor new test
 

diff --git a/sources b/sources
index 7ce662e..2ea857c 100644
--- a/sources
+++ b/sources
@@ -1 +1 @@
-SHA512 (scap-security-guide-0.1.80.tar.bz2) = 6cc80a8cc2dfdb175dcfeb39e0f4a6653bf879c955d39350d501977ead8d5fb86151bbf105b6cd2983cb51240c6ff102b18cd16d9125f5b75dd6b53ae5418227
+SHA512 (scap-security-guide-0.1.81.tar.bz2) = 11e26cfa96a6f1bd98b3a131837e2f86c9a9851239337d86d624b01627faf10f7a03c395a5839ddab018e0fa47719ade05a9946f90d5ca96b1261776a9164379

                 reply	other threads:[~2026-06-02 12:49 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=178040456428.1.12382492620158495448.rpms-scap-security-guide-287b196c303a@fedoraproject.org \
    --to=vpolasek@redhat.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