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 348d2aff Regen SBOM from commit
399860bdf68af7ca04eabdc03d98f666f3e3a70b
add 81a95edf Regen SBOM from commit
399860bdf68af7ca04eabdc03d98f666f3e3a70b (#2064)
add de7f7f65 Bump org.apache.activemq:artemis-jakarta-client-all (#2068)
add 6b992f0d Regen for commit de7f7f6596076635e5a8962d24adb1b933df9792
(#2070)
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 (348d2aff)
\
N -- N -- N refs/heads/regen_bot_sbom (6b992f0d)
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:
kamelets/jms-apache-artemis-sink.kamelet.yaml | 2 +-
kamelets/jms-apache-artemis-source.kamelet.yaml | 2 +-
kamelets/jms-pooled-apache-artemis-sink.kamelet.yaml | 2 +-
kamelets/jms-pooled-apache-artemis-source.kamelet.yaml | 2 +-
.../src/main/resources/kamelets/jms-apache-artemis-sink.kamelet.yaml | 2 +-
.../src/main/resources/kamelets/jms-apache-artemis-source.kamelet.yaml | 2 +-
.../main/resources/kamelets/jms-pooled-apache-artemis-sink.kamelet.yaml | 2 +-
.../resources/kamelets/jms-pooled-apache-artemis-source.kamelet.yaml | 2 +-
pom.xml | 2 +-
9 files changed, 9 insertions(+), 9 deletions(-)
