This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/org.junit-junit-bom-5.11.0
in repository https://gitbox.apache.org/repos/asf/logging-log4j-samples.git
discard 6017c3a Bump org.junit:junit-bom from 5.10.3 to 5.11.0
add a38c996 Update `org.springframework:spring-framework-bom` to version
`5.3.39` (#164)
add 8eb382c Update `net.bytebuddy:byte-buddy` to version `1.14.19` (#165)
add 2e7a1b8 Update `com.google.guava:guava` to version `33.3.0-jre` (#166)
add d2260cb Update `org.eclipse.jetty:jetty-maven-plugin` to version
`10.0.23` (#167)
add d0f9b1b Update `org.jetbrains.kotlin:kotlin-bom` to version `2.0.20`
(#168)
add e911f54 Bump org.junit:junit-bom from 5.10.3 to 5.11.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 (6017c3a)
\
N -- N -- N
refs/heads/dependabot/maven/org.junit-junit-bom-5.11.0 (e911f54)
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 | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
