This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/co.elastic.clients-elasticsearch-java-9.2.3
in repository https://gitbox.apache.org/repos/asf/syncope.git
discard b47589e429 Bump co.elastic.clients:elasticsearch-java from 9.2.2 to
9.2.3
add cdacfd59dd Bump org.mariadb.jdbc:mariadb-java-client from 3.5.6 to
3.5.7
add b50d1346a9 Upgrading Spring Cloud Gateway
add a425a0296d Upgrading OpenSearch
add 7c332c3220 Bump org.apache.commons:commons-jexl3 from 3.6.0 to 3.6.1
add a6faaf8e42 Aligning Tomcat version with Spring Boot's
add 00bcffbed6 Bump co.elastic.clients:elasticsearch-java from 9.2.2 to
9.2.3
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 (b47589e429)
\
N -- N -- N
refs/heads/dependabot/maven/co.elastic.clients-elasticsearch-java-9.2.3
(00bcffbed6)
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:
pom.xml | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
