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 9ab1b6c74 Regen SBOM from commit
9f4fbd3e8fdc90884f50149ba30a3cdd46a91838
add e85a4bc72 Regen SBOM from commit
9f4fbd3e8fdc90884f50149ba30a3cdd46a91838 (#2711)
add 5775d3fcb chore(deps): bump com.amazon.redshift:redshift-jdbc42 (#2713)
add f70792082 Regen SBOM from commit
5775d3fcb2ba7a8e8d4e0d9813cf03ca3eb9c222
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 (9ab1b6c74)
\
N -- N -- N refs/heads/regen_bot_sbom (f70792082)
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 | 74 ++++++++++++++--------------
camel-kamelets-sbom/camel-kamelets-sbom.xml | 74 ++++++++++++++--------------
kamelets/aws-redshift-sink.kamelet.yaml | 2 +-
kamelets/aws-redshift-source.kamelet.yaml | 2 +-
pom.xml | 2 +-
5 files changed, 77 insertions(+), 77 deletions(-)
