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 f5580a24 Regen SBOM from commit
02a115dbf231f783d0105f56f20dd8dc0e10795b
add 14140751 Regen SBOM from commit
02a115dbf231f783d0105f56f20dd8dc0e10795b
add ac35ff58 Issue-981: Improve narrative for chatId.
add 1c65f878 Regen for commit ac35ff58a32e1807b3b70e521165401553b5ce4d
add 48feae4d Regen SBOM from commit
1c65f878e70c01c4f0515dde05df255befdba29c
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 (f5580a24)
\
N -- N -- N refs/heads/regen_bot_sbom (48feae4d)
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 | 4 ++--
camel-kamelets-sbom/camel-kamelets-sbom.xml | 4 ++--
kamelets/telegram-sink.kamelet.yaml | 3 ++-
.../src/main/resources/kamelets/telegram-sink.kamelet.yaml | 3 ++-
4 files changed, 8 insertions(+), 6 deletions(-)
