From: Peter Marko <peter.marko@siemens.com>
To: openembedded-core@lists.openembedded.org
Cc: peter.marko@siemens.com
Subject: [wrynose][RFC PATCH 09/11] python3-sbom-cve-check: update to version 1.3.3
Date: Sat, 8 Aug 2026 12:51:45 +0200 [thread overview]
Message-ID: <20260808105147.42294-10-peter.marko@siemens.com> (raw)
In-Reply-To: <20260808105147.42294-1-peter.marko@siemens.com>
From: Benjamin Robin <benjamin.robin@bootlin.com>
For details on this new release, see:
https://github.com/bootlin/sbom-cve-check/releases/tag/v1.3.3
Signed-off-by: Benjamin Robin (Schneider Electric) <benjamin.robin@bootlin.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
(From OE-Core rev: 7feb4e30ba17a4b0eb37a1c6dde671d4491bd35d)
Signed-off-by: Peter Marko <peter.marko@siemens.com>
---
...-sbom-cve-check_1.3.2.bb => python3-sbom-cve-check_1.3.3.bb} | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
rename meta/recipes-devtools/sbom-cve-check/{python3-sbom-cve-check_1.3.2.bb => python3-sbom-cve-check_1.3.3.bb} (82%)
diff --git a/meta/recipes-devtools/sbom-cve-check/python3-sbom-cve-check_1.3.2.bb b/meta/recipes-devtools/sbom-cve-check/python3-sbom-cve-check_1.3.3.bb
similarity index 82%
rename from meta/recipes-devtools/sbom-cve-check/python3-sbom-cve-check_1.3.2.bb
rename to meta/recipes-devtools/sbom-cve-check/python3-sbom-cve-check_1.3.3.bb
index f14901e300..2aca100569 100644
--- a/meta/recipes-devtools/sbom-cve-check/python3-sbom-cve-check_1.3.2.bb
+++ b/meta/recipes-devtools/sbom-cve-check/python3-sbom-cve-check_1.3.3.bb
@@ -5,7 +5,7 @@ LICENSE = "GPL-2.0-or-later"
LIC_FILES_CHKSUM = "file://LICENSE;md5=570a9b3749dd0463a1778803b12a6dce"
PYPI_PACKAGE = "sbom_cve_check"
-SRC_URI[sha256sum] = "0a7f07a0c6ce45d40adc6d311ddc25c4466f59bafcbce149b6fb3663791a5d89"
+SRC_URI[sha256sum] = "8b766be1ae92b4eceaa2f694dd4724e310886c6436f44267a6bbc6a7b81ab8b9"
inherit pypi python_hatchling
next prev parent reply other threads:[~2026-08-08 10:53 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-08 10:51 [wrynose][RFC PATCH 00/11] sbom-cve-check update Peter Marko
2026-08-08 10:51 ` [wrynose][RFC PATCH 01/11] sbom-cve-check-update-nvd-native: upgrade 2026.05.07-000006 -> 2026.06.09-000006 Peter Marko
2026-08-08 10:51 ` [wrynose][RFC PATCH 02/11] python3-shacl2code: upgrade 1.0.1 -> 1.1.0 Peter Marko
2026-08-08 10:51 ` [wrynose][RFC PATCH 03/11] python3-spdx-python-model: update from version 0.0.5 to 0.0.6 Peter Marko
2026-08-08 10:51 ` [wrynose][RFC PATCH 04/11] python3-sbom-cve-check: update to version 1.3.2 Peter Marko
2026-08-08 10:51 ` [wrynose][RFC PATCH 05/11] sbom-cve-check-update-cvelist-native: update to version 2026-06-24 Peter Marko
2026-08-08 10:51 ` [wrynose][RFC PATCH 06/11] sbom-cve-check-update-nvd-native: update to version 2026.06.24-000003 Peter Marko
2026-08-08 10:51 ` [wrynose][RFC PATCH 07/11] sbom-cve-check-update-cvelist-native: -> 2026-07-23 Peter Marko
2026-08-08 10:51 ` [wrynose][RFC PATCH 08/11] sbom-cve-check-update-nvd-native: -> 2026.07.23-000007 Peter Marko
2026-08-08 10:51 ` Peter Marko [this message]
2026-08-08 10:51 ` [wrynose][RFC PATCH 10/11] sbom-cve-check-update-cvelist-native: update to version 2026-08-03 Peter Marko
2026-08-08 10:51 ` [wrynose][RFC PATCH 11/11] sbom-cve-check-update-nvd-native: update to version 2026.08.03-000011 Peter Marko
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=20260808105147.42294-10-peter.marko@siemens.com \
--to=peter.marko@siemens.com \
--cc=openembedded-core@lists.openembedded.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