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

github-bot pushed a change to branch 
dependabot/maven/com.github.spotbugs-spotbugs-maven-plugin-4.4.2.2
in repository https://gitbox.apache.org/repos/asf/commons-parent.git.


 discard ff12627  Bump spotbugs-maven-plugin from 4.3.0 to 4.4.2.2
     add cc6536a  Bump biz.aQute.bndlib from 5.3.0 to 6.0.0 (#64)
     add ccbd555  Bump biz.aQute.bndlib from 5.3.0 to 6.0.0 #64.
     add b69709a  Bump actions/checkout from 2.3.4 to 2.3.5 (#66)
     add f51e72a  Bump actions/checkout from 2.3.4 to 2.3.5 #66.
     add fd58762  Bump japicmp-maven-plugin from 0.15.3 to 0.15.4 (#68)
     add ddd8efb  Bump japicmp-maven-plugin from 0.15.3 to 0.15.4 #68
     add a715d55  Normalize wording.
     add d0879bb  Bump spotbugs-maven-plugin from 4.3.0 to 4.4.2.2

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   (ff12627)
            \
             N -- N -- N   
refs/heads/dependabot/maven/com.github.spotbugs-spotbugs-maven-plugin-4.4.2.2 
(d0879bb)

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 |  2 +-
 pom.xml                     |  4 ++--
 src/changes/changes.xml     | 24 ++++++++++++------------
 3 files changed, 15 insertions(+), 15 deletions(-)

Reply via email to