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.1.0-beta7
in repository https://gitbox.apache.org/repos/asf/camel.git
discard 482ed9d6702 chore(deps): Bump
dev.langchain4j:langchain4j-community-dashscope
add e3b347881f0 chore(deps): Bump aws-java-sdk2-version from 2.31.66 to
2.31.67 (#18416)
add eedda34e8f7 chore(deps): Bump metrics-version from 4.2.32 to 4.2.33
(#18415)
add 76d5e2d95b6 chore(deps): Bump xmlunit-version from 2.10.2 to 2.10.3
(#18417)
add b5dea048e2e chore(deps): Bump huaweicloud-sdk-version from 3.1.152 to
3.1.153 (#18419)
add fe59abc1a84 chore(deps): Bump
com.google.apis:google-api-services-sheets (#18420)
add aa92c7c9dad 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 (482ed9d6702)
\
N -- N -- N
refs/heads/dependabot/maven/dev.langchain4j-langchain4j-community-dashscope-1.1.0-beta7
(aa92c7c9dad)
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 | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
