This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/org.apache.shiro-shiro-core-2.1.0
in repository https://gitbox.apache.org/repos/asf/airavata.git
omit 3bc0c10084 Bump org.apache.shiro:shiro-core from 2.0.4 to 2.1.0
add 47e821e0cf deps: bump log4j-core from 2.24.0 to 2.25.3 (#587)
add 49d74eac9d deps: align all log4j artifacts to 2.25.3 (#607)
add 0142fea17a deps: bump zookeeper from 3.9.4 to 3.9.5 (#591)
add 4009f1e04e deps: bump jackson-core from 2.19.1 to 2.21.1 (#590)
add 651d0589a0 Bump org.apache.shiro:shiro-core from 2.0.4 to 2.1.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 (3bc0c10084)
\
N -- N -- N
refs/heads/dependabot/maven/org.apache.shiro-shiro-core-2.1.0 (651d0589a0)
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 | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
