[commons-vfs] branch dependabot/maven/org.mockito-mockito-core-4.6.0 updated (36a33319 -> 2584eca8)

[gi...@apache.org]

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

github-bot pushed a change to branch dependabot/maven/org.mockito-mockito-core-4.6.0
in repository https://gitbox.apache.org/repos/asf/commons-vfs.git


 discard 36a33319 Bump mockito-core from 4.5.1 to 4.6.0
     add 2130cbb8 Small clean up
     add 10d90932 Bump mockito-core from 4.5.0 to 4.5.1 (#263)
     add 26556fb8 Bump mockito-core from 4.5.0 to 4.5.1 #263
     add 7424655b Bump hadoop.version from 3.3.2 to 3.3.3 (#262)
     add 99df0e32 Bump hadoop.version from 3.3.2 to 3.3.3 #262
     add 7e0c3184 Bump spotbugs-maven-plugin from 4.6.0.0 to 4.7.0.0 (#264)
     add 2584eca8 Bump mockito-core from 4.5.1 to 4.6.0

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   (36a33319)
            \
             N -- N -- N   refs/heads/dependabot/maven/org.mockito-mockito-core-4.6.0 (2584eca8)

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:
 .../java/org/apache/commons/vfs2/provider/DefaultFileContent.java   | 4 ++--
 pom.xml                                                             | 4 ++--
 src/changes/changes.xml                                             | 6 +++---
 3 files changed, 7 insertions(+), 7 deletions(-)