This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch regen_bot_sbom
in repository https://gitbox.apache.org/repos/asf/camel-kamelets.git
omit 5a1f1723 Regen SBOM from commit
e5d79284be2201ee32e94a79f7dffabd8f76175d
add 619d06e6 Regen SBOM from commit
e5d79284be2201ee32e94a79f7dffabd8f76175d (#1988)
add 589ad501 Bump commons-io:commons-io from 2.16.0 to 2.16.1 (#1989)
add 097eb47e Bump org.apache.camel.k:camel-k-crds from 2.2.0 to 2.3.0
(#1990)
add 241798a8 Bump org.apache.maven.plugins:maven-gpg-plugin from 3.2.2 to
3.2.3 (#1992)
add c98cef3b Regen SBOM from commit
241798a8aca5fce490041f356c09746cd5dd76a5
This update added new revisions after undoing existing revisions.
That is to say, some revisions that were in the old version of the
branch are not in the new version. This situation occurs
when a user --force pushes a change and generates a repository
containing something like this:
* -- * -- B -- O -- O -- O (5a1f1723)
\
N -- N -- N refs/heads/regen_bot_sbom (c98cef3b)
You should already have received notification emails for all of the O
revisions, and so the following emails describe only the N revisions
from the common base, B.
Any revisions marked "omit" are not gone; other references still
refer to them. Any revisions marked "discard" are gone forever.
No new revisions were added by this update.
Summary of changes:
camel-kamelets-sbom/camel-kamelets-sbom.json | 813 ++++++++++++++-------------
camel-kamelets-sbom/camel-kamelets-sbom.xml | 811 +++++++++++++-------------
library/kamelets-maven-plugin/pom.xml | 2 +-
pom.xml | 4 +-
4 files changed, 816 insertions(+), 814 deletions(-)
