Upgrade llama.cpp from b9990 to b10015#342
Merged
Merged
Conversation
…25655
Bump the pin in all four required places (GIT_TAG + LLAMA_TAG in
llama/CMakeLists.txt, README badge, CLAUDE.md pinned-version line + doc
references, and the LlamaCppVersion.LLAMA_CPP_VERSION constant).
Patch refresh: upstream #25655 ("server: add --cors-* options") rewrote the
CORS-proxy/tools warning region of tools/server/server.cpp that
0007-server-attach-http-frontend.patch relocates (introducing a warn_names
vector, an is_router_server branch and a new cors_origins=='*' security
warning), so 0007 no longer applied. Refreshed so
llama_server_register_common_routes() extracts only the route bindings, while
the per-caller experimental-feature warnings (incl. upstream's new cors_origins
warning) stay in llama_server() -- they depend on router state the shared helper
does not carry, preserving #25655 with no upstream-warning regression. Patches
0001-0003, 0006, 0008 apply unchanged; #25649's prompt-cache-ownership refactor
and #25504's arg.cpp log-flush touch regions outside every patch.
Append the b9990..b10015 rows to the breaking-changes history.
Verified locally: fresh cmake configure (all six patches apply fail-loud, TTS
extracted from tts.cpp @ b10015) + full cmake --build (jllama + jllama_test link
cleanly, confirming the refreshed 0007 server.cpp restructure compiles) + ctest
485/485 passing.
Co-Authored-By: Claude Opus 4.8 <[email protected]>
Claude-Session: https://claude.ai/code/session_01VEwuFTTgA1jrqMB2m24yqe
bernardladenthin
had a problem deploying
to
maven-central
July 15, 2026 07:03 — with 
GitHub Actions
Failure
GitHub Actions
Failure
bernardladenthin
had a problem deploying
to
startgate
July 15, 2026 07:03 — with
GitHub Actions
Error
GitHub Actions
Error
bernardladenthin
had a problem deploying
to
maven-central
July 15, 2026 07:03 — with
GitHub Actions
Failure
GitHub Actions
Failure
The b9986->b9990 bump (merged via PR #341) omitted its history rows, leaving a gap between b9984->b9986 and b9990->b10015. Backfill the analysis + verification rows from the upstream b9986...b9990 compare diff: additive-only (GGUF tensor-shape accessor #24405 + Minimax2 eagle3 model support + test harmonization), no patch-target or priority-8 file touched, all six patches apply unchanged. Co-Authored-By: Claude Opus 4.8 <[email protected]> Claude-Session: https://claude.ai/code/session_01VEwuFTTgA1jrqMB2m24yqe
bernardladenthin
had a problem deploying
to
maven-central
July 15, 2026 07:05 — with
GitHub Actions
Failure
GitHub Actions
Failure
bernardladenthin
had a problem deploying
to
maven-central
July 15, 2026 07:05 — with
GitHub Actions
Failure
GitHub Actions
Failure
bernardladenthin
had a problem deploying
to
startgate
July 15, 2026 07:05 — with
GitHub Actions
Error
GitHub Actions
Error
|
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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
0007-server-attach-http-frontend.patchto consolidate experimental-feature warnings into a single location inllama_server(), removing duplicate warning blocks from the sharedllama_server_register_common_routes()helperChanges
Version Bump
GIT_TAGinllama/CMakeLists.txtfromb9990tob10015LLAMA_CPP_VERSIONconstant inllama/src/main/java/net/ladenthin/llama/value/LlamaCppVersion.javaCLAUDE.md,README.md, and build documentationPatch Refactoring (0007-server-attach-http-frontend.patch)
The patch was refined to better separate concerns:
llama_server_register_common_routes()): Registers HTTP routes for CORS proxy, built-in tools, and health/slots endpoints without logging experimental-feature warningsllama_server()): Consolidated all experimental-feature warnings (CORS, router mode, MCP proxy, built-in tools) into a single unified warning block that depends on router state, which the shared helper does not carryThis refactoring ensures warnings are logged only once per server startup and only in the context where router state is available, while allowing the route registration logic to be safely shared across standalone, router, and attach modes.
Test plan
PATCH_COMMAND)Related issues / PRs
Routine llama.cpp version bump as part of ongoing upstream tracking.
Checklist
CONTRIBUTING.mdandCODE_OF_CONDUCT.mdhttps://claude.ai/code/session_01VEwuFTTgA1jrqMB2m24yqe