[camel-quarkus] branch upgrade-camel-3.13.0 updated (ce33c90 -> b8712f3)

[ja...@apache.org]

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

jamesnetherton pushed a change to branch upgrade-camel-3.13.0
in repository https://gitbox.apache.org/repos/asf/camel-quarkus.git.


 discard ce33c90  Disable docs xref checks until #3307 is fixed
 discard 2bbc555  Disable MicroProfileHealthTest.testFailureThreshold due to #3277
 discard 5274d65  Disable AtlasMap native tests due to #3189
 discard 7cf6ff0  Use hard coded azure-bom version property since it has been removed from camel-parent & camel-dependencies
 discard 6908215  Upgrade Camel to 3.13.0
     add b40aa1c  Upgrade Camel to 3.13.0
     add d821c0a  Use hard coded azure-bom version property since it has been removed from camel-parent & camel-dependencies
     add d46e649  Disable AtlasMap native tests due to #3189
     add 04f1cdb  Disable MicroProfileHealthTest.testFailureThreshold due to #3277
     add b8712f3  Disable docs xref checks until #3307 is fixed

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   (ce33c90)
            \
             N -- N -- N   refs/heads/upgrade-camel-3.13.0 (b8712f3)

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:
 pom.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)