fix(deps): pin llama-cpp-2 to =0.1.102 to fix CI build failure #1797
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.
Summary
Pins
llama-cpp-2crate to exact version0.1.102to fix CI build failures on all PRs.Problem
After the recent
cargo update(commit b774aa9),llama-cpp-2was upgraded from0.1.102to0.1.127. Version0.1.126+introduced a breaking API change where thec_chartype changed from*const i8to*const u8, causing type mismatch errors:This affects all PRs during the
:packages:graalvm:buildRustNativesForHosttask in thelocal-aipackage.Solution
Pin the version exactly using
=0.1.102inCargo.tomlto prevent cargo from resolving to incompatible newer versions.Changes
Cargo.toml: Changedversion = "0.1.102"toversion = "=0.1.102"Cargo.lock: Downgraded from0.1.127to0.1.102Fixes
Fixes #1796