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.3
in repository https://gitbox.apache.org/repos/asf/camel.git
omit 0cf36f95968 chore(deps): Bump micrometer-tracing-version from 1.4.2 to
1.4.3
add 4601117a8b6 chore(deps): Bump micrometer-version from 1.14.3 to 1.14.4
(#17107)
add 0ce7d1cdd13 Ignoring log4j2-test.xml in infinispan-common test jar
(#17106)
add dbd904b5409 chore(deps): Bump aws-java-sdk2-version from 2.30.16 to
2.30.17 (#17108)
add 7bb99ba11f4 chore(deps): Bump com.ibm.cloud:cloudant from 0.10.0 to
0.10.1 (#17109)
add 60ffe6730c1 chore(deps): Bump micrometer-tracing-version from 1.4.2 to
1.4.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 (0cf36f95968)
\
N -- N -- N
refs/heads/dependabot/maven/micrometer-tracing-version-1.4.3 (60ffe6730c1)
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:
.../src/test/resources/log4j2.component.properties | 2 +-
parent/pom.xml | 6 +++---
2 files changed, 4 insertions(+), 4 deletions(-)
copy catalog/camel-catalog/src/main/resources/META-INF/version.properties =>
components/camel-infinispan/camel-infinispan-embedded/src/test/resources/log4j2.component.properties
(95%)
