This is an automated email from the ASF dual-hosted git repository.
pkarwasz pushed a change to branch dependabot/maven/main/mockito.version-5.2.0
in repository https://gitbox.apache.org/repos/asf/logging-log4j2.git
omit 0c2a7c1d56 Switch from `inline` to legacy `subclass` mockmaker
omit 8013d208f4 Bump mockito.version from 4.11.0 to 5.2.0
add 2bf0f759d4 Bump actions/setup-java from 3.11.0 to 3.12.0 (#1603)
add 2de82172a6 Bump spring-boot.version from 2.7.10 to 2.7.14 (#1618)
new 2ebc356a32 Bump mockito.version from 4.11.0 to 5.2.0
new 8d3e64b9d8 Switch from `inline` to legacy `subclass` mockmaker
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 (0c2a7c1d56)
\
N -- N -- N
refs/heads/dependabot/maven/main/mockito.version-5.2.0 (8d3e64b9d8)
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.
The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
.github/workflows/benchmark.yml | 4 ++--
.github/workflows/build.yml | 4 ++--
.github/workflows/codeql-analysis.yml | 2 +-
.github/workflows/log4j-kafka-test.yml | 2 +-
pom.xml | 2 +-
5 files changed, 7 insertions(+), 7 deletions(-)
