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

dependabot[bot] pushed a change to branch 
dependabot/maven/org.codehaus.gmavenplus-gmavenplus-plugin-5.0.0
in repository https://gitbox.apache.org/repos/asf/shiro.git


    omit ce13d79b0 chore(deps): bump org.codehaus.gmavenplus:gmavenplus-plugin
    omit d5bf2249e chore(asf.yaml): fix shiro-private name
    omit 49cd83b29 chore(asf): another asf.yaml fix
     add b9fd89f38 chore(deps): bump org.codehaus.gmavenplus:gmavenplus-plugin

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   (ce13d79b0)
            \
             N -- N -- N   
refs/heads/dependabot/maven/org.codehaus.gmavenplus-gmavenplus-plugin-5.0.0 
(b9fd89f38)

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:
 .asf.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

Reply via email to