Skip to content

Upgrade llama.cpp from b9637 to b9642#237

Merged
bernardladenthin merged 1 commit into
mainfrom
claude/vibrant-franklin-yr0buy
Jun 15, 2026
Merged

Upgrade llama.cpp from b9637 to b9642#237
bernardladenthin merged 1 commit into
mainfrom
claude/vibrant-franklin-yr0buy

Conversation

@bernardladenthin

Copy link
Copy Markdown
Owner

Summary

  • Upgrade llama.cpp dependency from b9637 to b9642
  • Update all references in documentation and build configuration
  • Add breaking changes documentation for the new version range

Test plan

  • CI is green on this branch
  • Docs / CHANGELOG updated where applicable

Related issues / PRs

None

Checklist

  • I have read CONTRIBUTING.md and CODE_OF_CONDUCT.md
  • My commits follow Conventional Commits
  • No security-sensitive changes (if there are, I have notified the maintainer privately per SECURITY.md)

Notes

The upgrade includes internal backend changes to CUDA, WebGPU, and WebUI components that do not affect the jllama project's public API or compilation. All changes are documented in docs/history/llama-cpp-breaking-changes.md for future reference during version bumps.

https://claude.ai/code/session_01QxDa7gWwDD4spg8xFbMHqS

No project source changes required — the b9637..b9642 range only touches
the CUDA/WebGPU backends, the Python LoRA converter, an upstream backend-ops
test, and the WebUI. None of the headers consumed by jllama.cpp / server-*
/ utils.hpp changed.

- CMakeLists.txt: GIT_TAG b9637 -> b9642
- README.md: badge + release link
- CLAUDE.md: pinned-version line + FetchContent note
- docs/history: appended b9637..b9642 breaking-changes rows
@bernardladenthin bernardladenthin merged commit 20ab7c3 into main Jun 15, 2026
8 of 10 checks passed
@bernardladenthin bernardladenthin deleted the claude/vibrant-franklin-yr0buy branch June 15, 2026 11:35
@sonarqubecloud

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants