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 5826a4f4 Regen SBOM from commit
75d7865e3106c88316886ef0a9a689e93f62b327
add 49ef8505 Regen SBOM from commit
75d7865e3106c88316886ef0a9a689e93f62b327 (#2244)
add 79697df5 Bump org.messaginghub:pooled-jms from 3.1.6 to 3.1.7 (#2245)
add e333cd00 Regen for commit 79697df5714e7b1c3e549253bbf477c232cf4574
(#2246)
add 4084c9e0 Updated CHANGELOG.md
add c2213a4d Bump org.apache.maven.resolver:maven-resolver-api from 2.0.1
to 2.0.2 (#2250)
add 83ff1406 Updated CHANGELOG.md
add c101b57d Regen SBOM from commit
83ff14067529043c52798890082aacfa5b7b39f4
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 (5826a4f4)
\
N -- N -- N refs/heads/regen_bot_sbom (c101b57d)
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:
CHANGELOG.md | 4 ++
camel-kamelets-sbom/camel-kamelets-sbom.json | 72 +++++++++++-----------
camel-kamelets-sbom/camel-kamelets-sbom.xml | 72 +++++++++++-----------
.../jms-pooled-apache-artemis-sink.kamelet.yaml | 2 +-
.../jms-pooled-apache-artemis-source.kamelet.yaml | 2 +-
.../jms-pooled-apache-artemis-sink.kamelet.yaml | 2 +-
.../jms-pooled-apache-artemis-source.kamelet.yaml | 2 +-
library/kamelets-maven-plugin/pom.xml | 2 +-
pom.xml | 2 +-
9 files changed, 82 insertions(+), 78 deletions(-)
