This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/micrometer-tracing-version-1.4.5
in repository https://gitbox.apache.org/repos/asf/camel.git
discard da242162378 chore(deps): Bump micrometer-tracing-version from 1.4.4 to
1.4.5
add 648c00a9a72 chore(deps): Bump junit-jupiter-version from 5.12.1 to
5.12.2
add 12ba50c1843 chore(deps-dev): Bump com.google.code.gson:gson from
2.12.1 to 2.13.0 (#17742)
add 9ae50379426 chore(deps): Bump aws-java-sdk2-version from 2.31.20 to
2.31.21 (#17739)
add 4bdccaa6177 chore(deps): Bump org.apache.santuario:xmlsec from 4.0.3
to 4.0.4 (#17744)
add 700de15fbb0 chore(deps): Bump org.jgroups:jgroups from 5.4.5.Final to
5.4.6.Final (#17745)
add cd753ca6ec3 chore(deps): Bump micrometer-version from 1.14.5 to 1.14.6
(#17741)
add 93e7ad96561 chore(deps): Bump micrometer-tracing-version from 1.4.4 to
1.4.5
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 (da242162378)
\
N -- N -- N
refs/heads/dependabot/maven/micrometer-tracing-version-1.4.5 (93e7ad96561)
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:
parent/pom.xml | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
