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.1.4
in repository https://gitbox.apache.org/repos/asf/camel.git
discard 504cd086103 chore(deps): Bump elasticsearch-java-client-version from
9.1.3 to 9.1.4
add 6c000ee7560 chore(deps-dev): Bump com.google.cloud:google-cloud-core
(#19256)
add 55a2a5583be chore(deps): Bump google-auth-library-oauth2-http-version
(#19257)
add bf4cbac1488 chore(deps): Bump opentelemetry-version from 1.54.0 to
1.54.1 (#19258)
add 66d5a8dc07b chore(deps): Bump elasticsearch-java-client-version from
9.1.3 to 9.1.4
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 (504cd086103)
\
N -- N -- N
refs/heads/dependabot/maven/elasticsearch-java-client-version-9.1.4
(66d5a8dc07b)
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(-)
