This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch dependabot/maven/micrometer-version-1.15.1
in repository https://gitbox.apache.org/repos/asf/camel.git
discard 4a665bf8204 chore(deps): Bump micrometer-version from 1.15.0 to 1.15.1
add bfe0613c604 chore(deps): Bump aws-java-sdk2-version from 2.31.59 to
2.31.60
add e66f9959bf1 chore(deps-dev): Bump io.projectreactor:reactor-core from
3.7.6 to 3.7.7 (#18330)
add 12224ddd453 chore(deps): Bump mongo-java-driver-version from 5.5.0 to
5.5.1 (#18331)
add 9038dc5f5c3 chore(deps): Bump micrometer-tracing-version from 1.5.0 to
1.5.1 (#18329)
add f1f28971f35 chore(deps): Bump micrometer-version from 1.15.0 to 1.15.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 (4a665bf8204)
\
N -- N -- N
refs/heads/dependabot/maven/micrometer-version-1.15.1 (f1f28971f35)
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(-)
