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.1
in repository https://gitbox.apache.org/repos/asf/cxf.git
discard 7ee67e6a52 Bump cxf.micrometer-tracing.version from 1.4.6 to 1.5.1
add 3fcb8c500d Bump org.webjars:swagger-ui from 5.22.0 to 5.24.0 (#2448)
add c0d42fd697 Update Micrometer to 1.14.8
add a2aafe98e0 Update Micrometer Tracing to 1.4.7
add 20cd5a3439 Update Project Reactor to 3.7.7
add fb6e2f0602 Bump cxf.micrometer-tracing.version from 1.4.6 to 1.5.1
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 (7ee67e6a52)
\
N -- N -- N
refs/heads/dependabot/maven/cxf.micrometer-tracing.version-1.5.1 (fb6e2f0602)
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 | 2 +-
parent/pom.xml | 6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
