This is an automated email from the ASF dual-hosted git repository.
github-actions[bot] pushed a change to branch automatic-periodic-sync
in repository https://gitbox.apache.org/repos/asf/camel-spring-boot.git
omit 98cdb9774eb [create-pull-request] automated change
add b022b56511f [create-pull-request] automated change (#1890)
add e68afdb7730 Regen
add 25d45bea132 feat(starters): micrometer support
logMetricsOnShutdownFormat
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 (98cdb9774eb)
\
N -- N -- N refs/heads/automatic-periodic-sync (25d45bea132)
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:
.../springboot/catalog/components/langchain4j-agent.json | 6 ++++--
.../springboot/catalog/components/langchain4j-chat.json | 4 +++-
.../catalog/components/langchain4j-embeddings.json | 8 +++++---
.../springboot/catalog/components/langchain4j-tools.json | 4 +++-
.../camel-micrometer-starter/src/main/docs/micrometer.json | 6 ++++++
.../springboot/metrics/CamelMetricsAutoConfiguration.java | 3 +++
.../springboot/metrics/CamelMetricsConfiguration.java | 13 +++++++++++++
.../ObservabilityServicesEnvironmentPostProcessor.java | 3 ++-
.../ObservabilityServicesEnvironmentPostProcessorTest.java | 4 +++-
.../spring-boot/modules/ROOT/pages/starters/micrometer.adoc | 3 ++-
tooling/camel-spring-boot-dependencies/pom.xml | 10 ++++++++++
11 files changed, 54 insertions(+), 10 deletions(-)
