Bump quarkiverse-langchain4j.version from 0.22.0 to 0.23.0 #6894
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![dependabot[bot]](https://avatars.githubusercontent.com/in/29110?s=60&v=4){kind=small}
Bumps `quarkiverse-langchain4j.version` from 0.22.0 to 0.23.0. Updates `io.quarkiverse.langchain4j:quarkus-langchain4j-core` from 0.22.0 to 0.23.0 Updates `io.quarkiverse.langchain4j:quarkus-langchain4j-core-deployment` from 0.22.0 to 0.23.0 Updates `io.quarkiverse.langchain4j:quarkus-langchain4j-ollama` from 0.22.0 to 0.23.0 --- updated-dependencies: - dependency-name: io.quarkiverse.langchain4j:quarkus-langchain4j-core dependency-type: direct:production update-type: version-update:semver-minor - dependency-name: io.quarkiverse.langchain4j:quarkus-langchain4j-core-deployment dependency-type: direct:production update-type: version-update:semver-minor - dependency-name: io.quarkiverse.langchain4j:quarkus-langchain4j-ollama dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <[email protected]>
dependabot
bot
added
dependencies
|
Warning Branch auto synchronized due to changes in generated files. New workflow run triggered: https://github.com/apache/camel-quarkus/actions/runs/12659606706 Please check the workflow result before merging. |
|
Windows tests are failing with stack trace below: @zbendhiba Dev service should not be triggered during langchain4j-chat tests ? As we intend to use mock. Then, the issue could probably be linked to |
|
I think @jamesnetherton introduced mock because Ollama dev services take too much time to load a model, and it's too slow for CI tests. In Camel core the integration tests are disabled in CI. |
|
To get this merged, maybe we just disable dev services in the test modules until we have a better way? |
+1 for that |
|
It's still unclear as for instance windows tests are running well for langchain4j itests but not langchain4j-chat. Let's attempt to disable dev services for langchain4j-chat and see. |
|
So, disabling ollama dev services for langchain4j-chat makes the pr build happy. And the wiremocked tests for both langchain and langchain4j-chat are running well. From there, merging seems ok unless one has a compelling reason not to. @jamesnetherton How do we generally merge dependabot patched pr ? Simply click |
Yeah, always squash for Dependabot where there are multiple commits. Makes it easier to roll back. |
aldettinger
deleted the
dependabot/maven/quarkiverse-langchain4j.version-0.23.0
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Bumps
quarkiverse-langchain4j.versionfrom 0.22.0 to 0.23.0.Updates
io.quarkiverse.langchain4j:quarkus-langchain4j-corefrom 0.22.0 to 0.23.0Updates
io.quarkiverse.langchain4j:quarkus-langchain4j-core-deploymentfrom 0.22.0 to 0.23.0Updates
io.quarkiverse.langchain4j:quarkus-langchain4j-ollamafrom 0.22.0 to 0.23.0Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)