This is an automated email from the ASF dual-hosted git repository.

github-bot pushed a change to branch 
dependabot-maven-org.apache.maven-maven-core-3.9.12
in repository https://gitbox.apache.org/repos/asf/ozone.git


    omit e2ffb1cae55 Bump org.apache.maven:maven-core from 3.9.10 to 3.9.12
     add 892ceb56c47 HDDS-14632. TestDefault...ChoosingPolicy failing due to 
cluster ID mismatch (#9761)
     add 135d58a061d HDDS-14633. ozonescripts/test.sh fails with image already 
exists (#9762)
     add 89fd22f6ec5 Bump org.apache.maven:maven-core from 3.9.10 to 3.9.12

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   (e2ffb1cae55)
            \
             N -- N -- N   
refs/heads/dependabot-maven-org.apache.maven-maven-core-3.9.12 (89fd22f6ec5)

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:
 .../container/diskbalancer/TestDefaultContainerChoosingPolicy.java   | 3 +++
 .../container/diskbalancer/TestDefaultVolumeChoosingPolicy.java      | 5 ++---
 .../ozone/container/upgrade/TestDatanodeUpgradeToSchemaV3.java       | 4 +++-
 hadoop-ozone/dist/src/main/compose/ozone-om-ha/docker-compose.yaml   | 5 -----
 hadoop-ozone/dist/src/main/compose/ozonescripts/docker-compose.yaml  | 3 ---
 5 files changed, 8 insertions(+), 12 deletions(-)


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to