This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/org.elasticsearch.client-elasticsearch-rest-client-sniffer-9.2.0
in repository https://gitbox.apache.org/repos/asf/camel.git
discard 8a21a850cbcd chore(deps): Bump
org.elasticsearch.client:elasticsearch-rest-client-sniffer
add 6c27869f7c5b chore(deps): Bump aws-java-sdk2-version from 2.36.0 to
2.36.1 (#19683)
add fc47419f7007 chore(deps): Bump huaweicloud-sdk-version from 3.1.170 to
3.1.171 (#19684)
add 8eb6e525dffb chore(deps): Bump
com.google.cloud:google-cloud-pubsublite (#19685)
add 2ab275ddd159 chore(deps): Bump jandex-version from 3.5.0 to 3.5.1
(#19688)
add 8670ace1a9cd chore(deps): Bump elasticsearch-java-client-version from
9.1.5 to 9.2.0 (#19686)
add e29a4a8caebb chore(deps): Bump
org.elasticsearch.client:elasticsearch-rest-client-sniffer
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 (8a21a850cbcd)
\
N -- N -- N
refs/heads/dependabot/maven/org.elasticsearch.client-elasticsearch-rest-client-sniffer-9.2.0
(e29a4a8caebb)
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(-)
