This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/elasticsearch-java-client-version-9.2.1
in repository https://gitbox.apache.org/repos/asf/camel.git
discard 97ce3ecebe8a chore(deps): Bump elasticsearch-java-client-version from
9.2.0 to 9.2.1
add 54b291c231a7 chore(deps): Bump bytebuddy-version from 1.17.8 to 1.18.1
(#19907)
add ce6d81a4e695 chore(deps): Bump jetty-version from 12.1.3 to 12.1.4
(#19908)
add 4b022a89191a chore(deps): Bump
org.elasticsearch.client:elasticsearch-rest-client-sniffer (#19905)
add 2a5d26575acd chore(deps): Bump elasticsearch-java-client-version from
9.2.0 to 9.2.1
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 (97ce3ecebe8a)
\
N -- N -- N
refs/heads/dependabot/maven/elasticsearch-java-client-version-9.2.1
(2a5d26575acd)
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 | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
