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 4094dcf1a Regen SBOM from commit
0c44a59967ae5c5cb961577dc95d2ec48fa37eec
add 1d8e8e746 Regen SBOM from commit
0c44a59967ae5c5cb961577dc95d2ec48fa37eec (#2611)
add c9ec70135 Bump com.amazon.redshift:redshift-jdbc42 from 2.1.0.34 to
2.2.0 (#2613)
add af32a6a0d Regen for commit c9ec7013566fae714dca379796dda554c6b86b0b
(#2614)
add b4a7e8f22 Bump org.apache.maven.resolver:maven-resolver-api from
2.0.11 to 2.0.13 (#2612)
add e1221904d Regen SBOM from commit
b4a7e8f22076f31f4ed7aec1321dd7243339a233
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 (4094dcf1a)
\
N -- N -- N refs/heads/regen_bot_sbom (e1221904d)
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 | 40 +++++++++++-----------
camel-kamelets-sbom/camel-kamelets-sbom.xml | 40 +++++++++++-----------
kamelets/aws-redshift-sink.kamelet.yaml | 2 +-
kamelets/aws-redshift-source.kamelet.yaml | 2 +-
.../kamelets/aws-redshift-sink.kamelet.yaml | 2 +-
.../kamelets/aws-redshift-source.kamelet.yaml | 2 +-
library/kamelets-maven-plugin/pom.xml | 2 +-
pom.xml | 2 +-
8 files changed, 46 insertions(+), 46 deletions(-)
