This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/log4j.version-2.24.0
in repository https://gitbox.apache.org/repos/asf/logging-log4j-samples.git
discard 3d710f0 Bump log4j.version from 0.0.0-SNAPSHOT to 2.24.0
add c8a83c8 Update `ch.qos.logback:logback-classic` to version `1.5.8`
(#178)
add 8f0fd7f Update `org.graalvm.buildtools:native-maven-plugin` to
version `0.10.3` (#179)
add 914fe60 Update `org.eclipse.jetty:jetty-maven-plugin` to version
`11.0.0` (#181)
add 992d58b Update `org.eclipse.jetty:jetty-maven-plugin` to version
`11.0.24` (#182)
add b4e1d31 Update `apache/logging-parent` to version `` (#183)
add 65fcacf Update `org.apache.logging:logging-parent` to version
`11.3.0` (#184)
add ca937e1 Update `org.apache.logging:logging-parent` to version
`11.3.0` (#185)
add 3e5bbec Update `com.google.guava:guava` to version `33.3.1-jre` (#186)
add 3bfc988 Update to Log4j `2.24.1` RC1
add 8e687c7 Bump log4j.version from 0.0.0-SNAPSHOT to 2.24.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 (3d710f0)
\
N -- N -- N refs/heads/dependabot/maven/log4j.version-2.24.0
(8e687c7)
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 | 2 +-
.github/workflows/merge-dependabot.yaml | 4 ++--
log4j-samples-graalvm/pom.xml | 6 +++---
pom.xml | 20 ++++++++++++++++----
4 files changed, 22 insertions(+), 10 deletions(-)
