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 e1221904d Regen SBOM from commit
b4a7e8f22076f31f4ed7aec1321dd7243339a233
add a6ffeee17 Bump org.apache.rat:apache-rat-plugin from 0.16.1 to 0.17
(#2617)
add 90e5a726d Bump org.apache.activemq:artemis-jakarta-client-all (#2615)
add f0ca813e2 Regen SBOM from commit
b4a7e8f22076f31f4ed7aec1321dd7243339a233 (#2616)
add 0beb8c50c Regen for commit f0ca813e29ae6ea14b1de494378f523be9547e5c
(#2618)
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 (e1221904d)
\
N -- N -- N refs/heads/regen_bot_sbom (0beb8c50c)
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 +-
.../main/resources/kamelets/jms-apache-artemis-source.kamelet.yaml | 2 +-
.../resources/kamelets/jms-pooled-apache-artemis-sink.kamelet.yaml | 2 +-
.../resources/kamelets/jms-pooled-apache-artemis-source.kamelet.yaml | 2 +-
pom.xml | 4 ++--
9 files changed, 10 insertions(+), 10 deletions(-)
