This is an automated email from the ASF dual-hosted git repository.
dependabot[bot] pushed a change to branch dependabot/maven/micrometer-45580c05b2
in repository https://gitbox.apache.org/repos/asf/camel.git
discard bc3d48f3dcf2 chore(deps): Bump the micrometer group with 9 updates
add e40225d85808 chore(camel-test-infra-observability): upgrade
observability.prometheus.container to v3.14.0
add dd50979547a5 chore(camel-test-infra-observability): upgrade
observability.victoriatraces.container to v0.11.0
add 0e93052d495c Regen
add d2357ae03e91 chore(deps): Bump the micrometer group across 1 directory
with 9 updates
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 (bc3d48f3dcf2)
\
N -- N -- N refs/heads/dependabot/maven/micrometer-45580c05b2
(d2357ae03e91)
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:
.../org/apache/camel/component/sql/SqlOutputType.java | 18 +++++++++---------
.../infra/observability/services/container.properties | 4 ++--
2 files changed, 11 insertions(+), 11 deletions(-)
