(camel) branch it updated (6f8cdeaec659 -> 3dbf52ed4288)

[da...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

davsclaus pushed a change to branch it
in repository https://gitbox.apache.org/repos/asf/camel.git


 discard 6f8cdeaec659 CAMEL-22703: camel-jbang - history to have it mode to show message data like debugger
 discard f5ff406240d5 CAMEL-22703: camel-jbang - history to have it mode to show message data like debugger
 discard 7f82aea6dbb9 CAMEL-22703: camel-jbang - history to have it mode to show message data like debugger
 discard 2473ee4a88f3 CAMEL-22703: camel-jbang - history to have it mode to show message data like debugger
 discard 5eb4c4845769 CAMEL-22758: camel-jbang - Debug inside choice may not correlate to source location
 discard 775c62234a36 CAMEL-22758: camel-jbang - Debug inside choice may not correlate to source location
 discard 37872879bb76 CAMEL-22703: camel-jbang - history to have it mode to show message data like debugger
     add 5cfde670bff7 CAMEL-22757: camel-tika - Upgrade to tika 3.2.3 from 2.9.4
     add c9d0377e23ad Regen SBOM from commit 5cfde670bff72034749ff7a79b9f8e962c8345e1 (#20248)
     add 7c7a911d154b CAMEL-22703: camel-jbang - history to have it mode to show message data like debugger
     add 961d1d64c443 CAMEL-22758: camel-jbang - Debug inside choice may not correlate to source location
     add 8135d28ace20 CAMEL-22758: camel-jbang - Debug inside choice may not correlate to source location
     add e91deb38f2df CAMEL-22703: camel-jbang - history to have it mode to show message data like debugger
     add 0c248da34882 CAMEL-22703: camel-jbang - history to have it mode to show message data like debugger
     add 8bf837617f9b CAMEL-22703: camel-jbang - history to have it mode to show message data like debugger
     add 3dbf52ed4288 CAMEL-22703: camel-jbang - history to have it mode to show message data like debugger

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   (6f8cdeaec659)
            \
             N -- N -- N   refs/heads/it (3dbf52ed4288)

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-sbom/camel-sbom.json                         | 7175 ++++++++++++--------
 camel-sbom/camel-sbom.xml                          | 6522 ++++++++++--------
 .../ROOT/pages/camel-4x-upgrade-guide-4_10.adoc    |    6 +
 .../ROOT/pages/camel-4x-upgrade-guide-4_14.adoc    |    6 +
 4 files changed, 7822 insertions(+), 5887 deletions(-)