This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/1.13.x/org.apache.commons-commons-lang3-3.20.0
in repository https://gitbox.apache.org/repos/asf/shiro.git
discard 46d6adbe3 chore(deps): bump org.apache.commons:commons-lang3 from
3.19.0 to 3.20.0
add ad2b5bd37 chore(deps): bump org.codehaus.mojo:versions-maven-plugin
add c1ea51f07 Merge pull request #2397 from
apache/dependabot/maven/1.13.x/org.codehaus.mojo-versions-maven-plugin-2.20.1
add 32d7d490a chore(deps): bump org.apache.maven.plugins:maven-jar-plugin
add 06138d09b Merge pull request #2396 from
apache/dependabot/maven/1.13.x/org.apache.maven.plugins-maven-jar-plugin-3.5.0
add 79f8c25ba chore(deps): bump org.apache.commons:commons-lang3 from
3.19.0 to 3.20.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 (46d6adbe3)
\
N -- N -- N
refs/heads/dependabot/maven/1.13.x/org.apache.commons-commons-lang3-3.20.0
(79f8c25ba)
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(-)
