This is an automated email from the ASF dual-hosted git repository.
lprimak pushed a change to branch
dependabot/maven/org.jboss.arquillian.junit5-arquillian-junit5-container-1.9.0.Final
in repository https://gitbox.apache.org/repos/asf/shiro.git
omit 02589e709 deps: compatibility with Arquillian 1.9.0
omit 0302d8cf0 Merge branch 'main' into
dependabot/maven/org.jboss.arquillian.junit5-arquillian-junit5-container-1.9.0.Final
omit b1a0b3c35 chore(deps-dev): bump
org.jboss.arquillian.junit5:arquillian-junit5-container
add a0fab8a8d deps: compatibility with Arquillian 1.9.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 (02589e709)
\
N -- N -- N
refs/heads/dependabot/maven/org.jboss.arquillian.junit5-arquillian-junit5-container-1.9.0.Final
(a0fab8a8d)
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:
