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.0.2
in repository https://gitbox.apache.org/repos/asf/camel.git
discard 0064fc679ac chore(deps): Bump elasticsearch-java-client-version from
9.0.1 to 9.0.2
add 281597ac56f chore(deps): Bump aws-java-sdk2-version from 2.31.55 to
2.31.56 (#18258)
add b5c077fac54 chore(deps): Bump jetty-version from 12.0.21 to 12.0.22
(#18260)
add b9c11f995d0 chore(deps): Bump io.camunda:zeebe-client-java from 8.7.3
to 8.7.4 (#18264)
add 0501e0a07e4 chore(deps): Bump
org.elasticsearch.client:elasticsearch-rest-client-sniffer (#18268)
add db172b29fc3 chore(deps): Bump com.google.cloud:google-cloud-pubsub
(#18261)
add aa7cae5c15d chore(deps): Bump elasticsearch-java-client-version from
9.0.1 to 9.0.2
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 (0064fc679ac)
\
N -- N -- N
refs/heads/dependabot/maven/elasticsearch-java-client-version-9.0.2
(aa7cae5c15d)
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 | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
