This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/io.github.ascopes-protobuf-maven-plugin-4.0.2
in repository https://gitbox.apache.org/repos/asf/camel.git
omit a32d17097680 chore(deps): Bump io.github.ascopes:protobuf-maven-plugin
add 7a6a94746fab chore(deps): Bump com.cedarsoftware:java-util from 4.1.0
to 4.2.0
add ee59db3b5554 chore(deps-dev): Bump com.google.cloud:google-cloud-core
add f6a90759235d chore(deps): Bump milo-version from 1.0.7 to 1.0.8
add 576cf1067632 chore(deps): Bump org.neo4j.driver:neo4j-java-driver from
6.0.1 to 6.0.2
add d4c7f53a4aea fix(components): milvus not using lombok NotNull any
longer
add b5e4a43c2abe fix(ci): use artifactId instead of module dirname
add 348f2818b1b0 chore(deps): Bump io.github.ascopes:protobuf-maven-plugin
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 (a32d17097680)
\
N -- N -- N
refs/heads/dependabot/maven/io.github.ascopes-protobuf-maven-plugin-4.0.2
(348f2818b1b0)
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:
.github/actions/detect-dependencies/detect-test.sh | 13 +++++++------
.../LangChain4jEmbeddingsComponentMilvusTargetIT.java | 2 +-
components/camel-ai/camel-milvus/pom.xml | 9 ---------
.../camel/component/milvus/it/MilvusComponentIT.java | 4 ++--
parent/pom.xml | 14 +++++---------
5 files changed, 15 insertions(+), 27 deletions(-)
