This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/karaf-4.4.x/log4j.version-2.25.3
in repository https://gitbox.apache.org/repos/asf/karaf.git
discard 93f632877a Bump log4j.version from 2.24.3 to 2.25.3
add 49d78d6a41 Bump com.conversantmedia:disruptor from 1.2.20 to 1.2.21
(#2421)
add 20e1ecad32 Bump org.jacoco:jacoco-maven-plugin from 0.8.13 to 0.8.14
(#2415)
add 8a0ca358d7 Bump org.apache.maven.shared:maven-filtering from 3.3.0 to
3.5.0 (#2414)
add 6ac1ded5ba Bump org.apache.commons:commons-compress from 1.27.1 to
1.28.0 (#2412)
add 6e5fb2201e Bump maven.version from 3.9.12 to 3.9.14 (#2404)
add e564271d0d Bump org.codehaus.groovy:groovy-all from 3.0.3 to 3.0.25
(#2403)
add 45583674a8 Bump io.reactivex.rxjava3:rxjava from 3.1.5 to 3.1.12
(#2389)
add 81b3c4e567 Bump log4j.version from 2.24.3 to 2.25.3
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 (93f632877a)
\
N -- N -- N
refs/heads/dependabot/maven/karaf-4.4.x/log4j.version-2.25.3 (81b3c4e567)
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:
audit/pom.xml | 2 +-
examples/karaf-graphql-example/karaf-graphql-example-core/pom.xml | 2 +-
pom.xml | 6 +++---
tooling/karaf-maven-plugin/pom.xml | 4 ++--
4 files changed, 7 insertions(+), 7 deletions(-)
