This is an automated email from the ASF dual-hosted git repository.
github-bot 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
discard b55f16f0d chore(deps-dev): bump
org.jboss.arquillian.junit5:arquillian-junit5-container
add 7e9955afc chore(deps-dev): bump org.assertj:assertj-core from 3.26.0
to 3.26.3
add fcceb1aa0 Merge pull request #1580 from
apache/dependabot/maven/org.assertj-assertj-core-3.26.3
add 764e08b46 chore(deps): bump bytebuddy.version from 1.14.17 to 1.14.18
add ad164f199 Merge pull request #1579 from
apache/dependabot/maven/bytebuddy.version-1.14.18
add 7c454cba0 chore(deps): bump org.jsoup:jsoup from 1.17.2 to 1.18.1
add bf7ac7cd7 Merge pull request #1586 from
apache/dependabot/maven/org.jsoup-jsoup-1.18.1
add b1a0b3c35 chore(deps-dev): bump
org.jboss.arquillian.junit5:arquillian-junit5-container
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 (b55f16f0d)
\
N -- N -- N
refs/heads/dependabot/maven/org.jboss.arquillian.junit5-arquillian-junit5-container-1.9.0.Final
(b1a0b3c35)
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 ++--
support/jakarta-ee/pom.xml | 2 +-
2 files changed, 3 insertions(+), 3 deletions(-)
