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

github-bot pushed a change to branch 
dependabot/maven/org.apache.maven.plugins-maven-antrun-plugin-3.0.0
in repository https://gitbox.apache.org/repos/asf/commons-crypto.git.


 discard a62460d  Bump maven-antrun-plugin from 1.8 to 3.0.0
     add 0b1045e  Bump maven-checkstyle-plugin from 3.1.1 to 3.1.2
     add 417e911  Merge pull request #130 from 
apache/dependabot/maven/org.apache.maven.plugins-maven-checkstyle-plugin-3.1.2
     add 0643d97  Bump jmh.version from 1.12 to 1.27
     add 753082a  Merge pull request #119 from 
apache/dependabot/maven/jmh.version-1.27
     add 12e773f  Bump maven-antrun-plugin from 1.8 to 3.0.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   (a62460d)
            \
             N -- N -- N   
refs/heads/dependabot/maven/org.apache.maven.plugins-maven-antrun-plugin-3.0.0 
(12e773f)

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:
 pom.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

Reply via email to