This is an automated email from the ASF dual-hosted git repository.
github-bot pushed a change to branch
dependabot/maven/dev.langchain4j-langchain4j-community-dashscope-1.9.1-beta17
in repository https://gitbox.apache.org/repos/asf/camel.git
omit 1bec3e1c57b9 chore(deps): Bump
dev.langchain4j:langchain4j-community-dashscope
add de13e23669f9 chore(deps): Bump infinispan-version from 16.0.2 to
16.0.3 (#20118)
add b7ca3faf1e1d chore(deps): Bump io.milvus:milvus-sdk-java from 2.6.9 to
2.6.10 (#20119)
add 09c3468a5776 chore(deps): Bump
org.apache.maven.plugins:maven-war-plugin (#20122)
add eaf50dfef46c chore(deps): Bump com.apptasticsoftware:rssreader from
3.11.0 to 3.12.0 (#20121)
add ab8cbe11b0ed chore(deps): Bump langchain4j-beta-version (#20104)
add c9ec44b39a3b chore(deps): Bump langchain4j-version from 1.9.0 to 1.9.1
(#20107)
add 85022ad42529 Upgrade plugin and regen
add 06c19ec5f938 chore(deps): Bump
dev.langchain4j:langchain4j-community-dashscope
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 (1bec3e1c57b9)
\
N -- N -- N
refs/heads/dependabot/maven/dev.langchain4j-langchain4j-community-dashscope-1.9.1-beta17
(06c19ec5f938)
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:
.../modules/ROOT/pages/camel-report-maven-plugin.adoc | 5 ++---
parent/pom.xml | 14 +++++++-------
2 files changed, 9 insertions(+), 10 deletions(-)
