(camel) branch dependabot/maven/pulsar-version-4.0.6 updated (872137cce9c -> 0383c7f5e93)

[gi...@apache.org]

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

github-bot pushed a change to branch dependabot/maven/pulsar-version-4.0.6
in repository https://gitbox.apache.org/repos/asf/camel.git


 discard 872137cce9c chore(deps): Bump pulsar-version from 4.0.5 to 4.0.6
     add d82f35cb8dc chore(deps): Bump aws-java-sdk2-version from 2.32.12 to 2.32.13 (#18791)
     add 7ccde50fa5e chore(deps): Bump com.google.cloud:google-cloud-bigquery (#18792)
     add 7f30936a23e chore(deps): Bump org.apache.jackrabbit:jackrabbit-core (#18795)
     add fd188b6ecd3 chore(deps): Bump huaweicloud-sdk-version from 3.1.158 to 3.1.159 (#18796)
     add 7185cc9438f chore(deps): Bump com.googlecode.libphonenumber:libphonenumber (#18797)
     add d28ec78abd7 chore(deps): Bump com.pubnub:pubnub-gson from 10.5.5 to 10.5.7 (#18798)
     add fc638296bc3 chore(deps): Bump elasticsearch-java-client-version from 9.0.4 to 9.1.0 (#18793)
     add 0383c7f5e93 chore(deps): Bump pulsar-version from 4.0.5 to 4.0.6

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   (872137cce9c)
            \
             N -- N -- N   refs/heads/dependabot/maven/pulsar-version-4.0.6 (0383c7f5e93)

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:
 parent/pom.xml | 14 +++++++-------
 1 file changed, 7 insertions(+), 7 deletions(-)