[camel] branch regen_bot updated (2d33842c2ea -> a47a3b4d98b)

[gi...@apache.org]

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

github-bot pushed a change to branch regen_bot
in repository https://gitbox.apache.org/repos/asf/camel.git


    omit 2d33842c2ea Regen for commit 66674d6ca23dfb7b7da8b5b6d6eaa1bd8b1c8c9c
     add b7b9d796355 CAMEL-17902: Align MDC logging keys for traceId and spanId to be aligned with OpenTelemetry standard.
     add a47a3b4d98b Regen for commit b7b9d796355aae3ac1e895baf36b80d5c9403dc8

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   (2d33842c2ea)
            \
             N -- N -- N   refs/heads/regen_bot (a47a3b4d98b)

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:
 .../src/main/docs/opentelemetry.adoc                   |  4 +++-
 .../camel-opentracing/src/main/docs/opentracing.adoc   |  2 +-
 .../org/apache/camel/opentracing/MDCSupportTest.java   |  4 ++--
 .../org/apache/camel/tracing/ActiveSpanManager.java    |  4 ++--
 .../ROOT/pages/camel-3x-upgrade-guide-3_17.adoc        | 18 +++++++++++++-----
 5 files changed, 21 insertions(+), 11 deletions(-)