This is an automated email from the ASF dual-hosted git repository.
rgupta pushed a change to branch
dependabot/maven/org.apache.logging.log4j-log4j-bom-2.25.2
in repository https://gitbox.apache.org/repos/asf/logging-log4j-kotlin.git
discard e63d9c8 Bump org.apache.logging.log4j:log4j-bom from 2.24.3 to 2.25.2
add 6fbb4e5 Run PR workflows always, to match with required checks (#150)
add 66286e2 Document why spotbugs is disabled for the benchmark module
(#149)
add 8da2069 Document Maven issue with transitive log4j-api version
resolution (#147)
add 8e4f533 Bump org.apache.logging.log4j:log4j-bom from 2.24.3 to 2.25.2
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 (e63d9c8)
\
N -- N -- N
refs/heads/dependabot/maven/org.apache.logging.log4j-log4j-bom-2.25.2 (8e4f533)
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:
.github/workflows/build.yaml | 4 ----
log4j-api-kotlin-benchmark/pom.xml | 6 +++++-
src/site/antora/modules/ROOT/pages/index.adoc | 15 ++++++++++++++-
3 files changed, 19 insertions(+), 6 deletions(-)
