This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/cxf.micrometer-tracing.version-1.5.0
in repository https://gitbox.apache.org/repos/asf/cxf.git
discard 6087bbd726 Bump cxf.micrometer-tracing.version from 1.4.6 to 1.5.0
add cafbf431d2 Bump cxf.jetty.version from 12.0.20 to 12.0.21 (#2402)
add bf85ae46a5 Update Apache Tomcat to 10.1.41
add 316e7caddb Update Swagger Core to 2.2.31
add 2feeb7bdad Update Micrometer to 1.14.7
add 9a6702ad89 Update Project Reactor to 3.7.6
add 69749ce280 Bump cxf.micrometer-tracing.version from 1.4.6 to 1.5.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 (6087bbd726)
\
N -- N -- N
refs/heads/dependabot/maven/cxf.micrometer-tracing.version-1.5.0 (69749ce280)
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:
distribution/src/main/release/samples/pom.xml | 4 ++--
parent/pom.xml | 10 +++++-----
2 files changed, 7 insertions(+), 7 deletions(-)
