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

github-bot pushed a change to branch 
dependabot/maven/org.codehaus.plexus-plexus-resources-1.3.0
in repository https://gitbox.apache.org/repos/asf/maven-checkstyle-plugin.git


    omit ab1e92c  Bump org.codehaus.plexus:plexus-resources from 1.1.0 to 1.3.0
     add a96a4da  Bump org.codehaus.plexus:plexus-component-annotations
     add bf80148  Add .checkstyle to .gitignore
     add 6521c29  Bump org.codehaus.plexus:plexus-component-metadata from 2.1.1 
to 2.2.0 (#131)
     add 05df96b  Bump org.apache.commons:commons-lang3 from 3.12.0 to 3.14.0 
(#128)
     add 34fcf3e  Bump org.codehaus.mojo:build-helper-maven-plugin from 3.4.0 
to 3.5.0 (#127)
     add 7b412b6  Bump org.codehaus.plexus:plexus-resources from 1.1.0 to 1.3.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   (ab1e92c)
            \
             N -- N -- N   
refs/heads/dependabot/maven/org.codehaus.plexus-plexus-resources-1.3.0 (7b412b6)

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

Reply via email to