[commons-vfs] branch dependabot/maven/org.apache.ftpserver-ftpserver-core-1.2.0 updated (684fcf32 -> 58bbf26b)

[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.apache.ftpserver-ftpserver-core-1.2.0
in repository https://gitbox.apache.org/repos/asf/commons-vfs.git


    omit 684fcf32 Bump ftpserver-core from 1.1.2 to 1.2.0
     add 10d06201 Bump commons.pmd.version from 6.45.0 to 6.46.0 (#266)
     add b45d0619 Bump commons.pmd.version from 6.45.0 to 6.46.0 #266
     add 515b2c3d Add coverage.yml
     add 35ecb9d5 Bump spotbugs from 4.6.0 to 4.7.1 (#269)
     add a581c1ef Bump spotbugs from 4.6.0 to 4.7.1 #269
     add 1c43ad6f Bump commons.pmd.version from 6.46.0 to 6.47.0 (#270)
     add 58bbf26b Bump ftpserver-core from 1.1.2 to 1.2.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   (684fcf32)
            \
             N -- N -- N   refs/heads/dependabot/maven/org.apache.ftpserver-ftpserver-core-1.2.0 (58bbf26b)

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:
 .github/workflows/{maven.yml => coverage.yml} | 34 +++++++++++----------------
 pom.xml                                       |  4 ++--
 src/changes/changes.xml                       |  6 ++---
 3 files changed, 19 insertions(+), 25 deletions(-)
 copy .github/workflows/{maven.yml => coverage.yml} (65%)