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 8007b3b5a Regen SBOM from commit
7a90b70caf82cada1b6ef85ec08ba3eb5a855fb2
add f58d4ba35 Regen SBOM from commit
7a90b70caf82cada1b6ef85ec08ba3eb5a855fb2 (#2772)
add 949c0a9a7 Update google-mail-source expected header count to 9 (#2775)
add c40dbfb88 Regen for commit 949c0a9a740e5a4007fe39129e81e42975612910
(#2770)
add 03813bc9d Regen SBOM from commit
c40dbfb88273796c0dfe9fd17631351dfe504918
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 (8007b3b5a)
\
N -- N -- N refs/heads/regen_bot_sbom (03813bc9d)
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 | 158 ++++++++++-----------
camel-kamelets-sbom/camel-kamelets-sbom.xml | 158 ++++++++++-----------
.../kamelets/catalog/KameletsCatalogTest.java | 2 +-
.../kamelets/databricks-sink.kamelet.yaml | 2 +-
.../kamelets/databricks-source.kamelet.yaml | 2 +-
5 files changed, 161 insertions(+), 161 deletions(-)
