[camel-kamelets] branch regen_bot_sbom updated (391f14c9 -> 697ba5e2)

[gi...@apache.org]

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 391f14c9 Regen SBOM from commit 00bdc586dd65b83d5cff215f10fe91d098eefa3c
     add bb188cb9 Regen SBOM from commit 00bdc586dd65b83d5cff215f10fe91d098eefa3c (#1548)
     add 627aa18a Deploy with JDK 17 on CI Jenkins
     add 2d865d0a Updated CHANGELOG.md
     add 697ba5e2 Regen SBOM from commit 2d865d0aecfda218798f9c662ee8aa7e84851f2f

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   (391f14c9)
            \
             N -- N -- N   refs/heads/regen_bot_sbom (697ba5e2)

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:
 CHANGELOG.md                                 | 15 +++++++++++++++
 Jenkinsfile.deploy                           |  2 +-
 camel-kamelets-sbom/camel-kamelets-sbom.json |  4 ++--
 camel-kamelets-sbom/camel-kamelets-sbom.xml  |  4 ++--
 4 files changed, 20 insertions(+), 5 deletions(-)