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.4
in repository https://gitbox.apache.org/repos/asf/camel.git
discard 09556230dd3 chore(deps): Bump micrometer-tracing-version from 1.4.3 to
1.4.4
add 1658737c5a7 chore(deps): Bump com.ibm.cloud:cloudant from 0.10.1 to
0.10.2 (#17408)
add eafc0e1805d chore(deps): Bump micrometer-version from 1.14.4 to 1.14.5
(#17409)
add 64b096ce227 chore(deps): Bump aws-java-sdk2-version from 2.30.36 to
2.30.37 (#17410)
add 1499612d536 chore(deps): Bump com.github.mwiede:jsch from 0.2.23 to
0.2.24 (#17411)
add 9325f3d988f chore(deps): Bump micrometer-tracing-version from 1.4.3 to
1.4.4
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 (09556230dd3)
\
N -- N -- N
refs/heads/dependabot/maven/micrometer-tracing-version-1.4.4 (9325f3d988f)
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 | 8 ++++----
1 file changed, 4 insertions(+), 4 deletions(-)
