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 3cf3c668a Regen SBOM from commit
652c0a861d6ab56d2579c5e230d81608a9d6145e
add 78d393e1b Regen SBOM from commit
652c0a861d6ab56d2579c5e230d81608a9d6145e (#2767)
add f86330e5f chore(deps): bump com.databricks:databricks-jdbc from 3.2.1
to 3.3.1 (#2768)
add 7a90b70ca chore(deps): bump org.citrusframework:citrus-bom from 4.9.4
to 4.10.0 (#2769)
add 8007b3b5a Regen SBOM from commit
7a90b70caf82cada1b6ef85ec08ba3eb5a855fb2
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 (3cf3c668a)
\
N -- N -- N refs/heads/regen_bot_sbom (8007b3b5a)
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 | 112 +++++++++++++--------------
camel-kamelets-sbom/camel-kamelets-sbom.xml | 112 +++++++++++++--------------
kamelets/databricks-sink.kamelet.yaml | 2 +-
kamelets/databricks-source.kamelet.yaml | 2 +-
pom.xml | 4 +-
5 files changed, 116 insertions(+), 116 deletions(-)
