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

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


 discard a312679e4d Remove obserability-services config workaround for /observe 
endpoint tracing
 discard d824daabe2 Disable Micrometer JMX tests due to #6984
 discard 16c6df804a Upgrade Quarkus to 3.19.0.CR1
     add 947f76eba2 Enable azure-servicebus produceConsumeWithCustomClients test
     new b36b1190ba Upgrade Quarkus to 3.19.0.CR1
     new cbd641524a Disable Micrometer JMX tests due to #6984
     new 4be6ef9a35 Remove obserability-services config workaround for /observe 
endpoint tracing

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   (a312679e4d)
            \
             N -- N -- N   refs/heads/quarkus-main (4be6ef9a35)

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.

The 3 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.


Summary of changes:
 .../quarkus/component/azure/servicebus/it/AzureServiceBusRoutes.java  | 4 ----
 .../quarkus/component/azure/servicebus/it/AzureServiceBusTest.java    | 2 --
 2 files changed, 6 deletions(-)

Reply via email to