[shiro] branch dependabot/maven/org.codehaus.groovy-groovy-3.0.13 updated (909c660d -> e13cb8a8)

[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.codehaus.groovy-groovy-3.0.13
in repository https://gitbox.apache.org/repos/asf/shiro.git


 discard 909c660d Bump groovy from 3.0.9 to 3.0.13
     add 26ca9d8f Bump commons-lang3 from 3.9 to 3.12.0
     add 29f9f049 Merge pull request #436 from apache/dependabot/maven/org.apache.commons-commons-lang3-3.12.0
     add 2b540563 Bump junit.version from 5.8.1 to 5.9.1
     add f12c7b65 Merge pull request #435 from apache/dependabot/maven/junit.version-5.9.1
     add 262eade8 Bump hamcrest-core from 2.1 to 2.2
     add cbd393ed Merge pull request #434 from apache/dependabot/maven/org.hamcrest-hamcrest-core-2.2
     add e610e337 Bump easymock from 4.0.2 to 4.3
     add 8dd0a868 Merge pull request #432 from apache/dependabot/maven/org.easymock-easymock-4.3
     add e13cb8a8 Bump groovy from 3.0.9 to 3.0.13

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   (909c660d)
            \
             N -- N -- N   refs/heads/dependabot/maven/org.codehaus.groovy-groovy-3.0.13 (e13cb8a8)

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 | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)