This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/ambari-infra-solr-client/com.amazonaws-aws-java-sdk-s3-1.12.261
in repository https://gitbox.apache.org/repos/asf/ambari-infra.git
discard 29b9477 Bump aws-java-sdk-s3 in /ambari-infra-solr-client
add 543ea42 AMBARI-25723. Enable squash and merge in GitHub PR (#38)
add 25936d0 AMBARI-25203 Updated jackson-databind to 2.9.8 and
boucycastle libs to 1.61 (#37)
add 0060c84 Bump aws-java-sdk-s3 in /ambari-infra-solr-client
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 (29b9477)
\
N -- N -- N
refs/heads/dependabot/maven/ambari-infra-solr-client/com.amazonaws-aws-java-sdk-s3-1.12.261
(0060c84)
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:
.../main/resources/solrCloudCli.sh => .asf.yaml | 27 ++++++++++++----------
ambari-infra-manager-it/pom.xml | 8 +++++++
ambari-infra-manager/pom.xml | 17 ++++++++++++++
ambari-infra-solr-client/pom.xml | 16 +++++++++++++
ambari-infra-solr-plugin/pom.xml | 10 ++++++++
pom.xml | 6 ++---
6 files changed, 69 insertions(+), 15 deletions(-)
copy ambari-infra-solr-client/src/main/resources/solrCloudCli.sh => .asf.yaml
(69%)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@ambari.apache.org
For additional commands, e-mail: commits-h...@ambari.apache.org
