(shiro) branch dependabot/maven/commons-logging-commons-logging-1.3.0 updated (a2c5aba9d -> 4fb53973f)

[gi...@apache.org]

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

github-bot pushed a change to branch dependabot/maven/commons-logging-commons-logging-1.3.0
in repository https://gitbox.apache.org/repos/asf/shiro.git


    omit a2c5aba9d build(deps-dev): bump commons-logging:commons-logging from 1.2 to 1.3.0
     add b0747381e build(deps): bump org.apache.commons:commons-lang3 from 3.13.0 to 3.14.0
     add 67b99ef51 Merge pull request #1248 from apache/dependabot/maven/org.apache.commons-commons-lang3-3.14.0
     add 407b25e28 build(deps): bump groovy.version from 4.0.15 to 4.0.17
     add 0d4869aa6 Merge pull request #1250 from apache/dependabot/maven/groovy.version-4.0.17
     add 187a61681 build(deps): bump log4j.version from 2.21.1 to 2.22.0
     add f8c32eeaa Merge pull request #1246 from apache/dependabot/maven/log4j.version-2.22.0
     add 4fb53973f build(deps-dev): bump commons-logging:commons-logging from 1.2 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   (a2c5aba9d)
            \
             N -- N -- N   refs/heads/dependabot/maven/commons-logging-commons-logging-1.3.0 (4fb53973f)

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