Repository navigation
Sync shared files and pin net.ladenthin:llama to 6.0.0 - #226
Merged
Merged
Conversation
Every uses: reference carries the commit the tag resolved to, with the tag in a comment; Dependabot keeps them current. Kept byte-identical with the sibling repositories (shared-files.sha256 rewritten). Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MjAMq3jnoveX5dcvLGhNQw
java-llama.cpp never published 5.2.0; the natives split and the other breaking changes ship as 6.0.0 (decided 2026-10-15). The pin, the plugin README's snippets, the CI comments and the changelog follow; the build stays red until that release exists, as before. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MjAMq3jnoveX5dcvLGhNQw
Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MjAMq3jnoveX5dcvLGhNQw
…flag java-llama.cpp's natives check now holds the job that re-uploads the Windows natives artifacts signed (`overwrite: true`); the shared helper that renders an upload-artifact step grew the parameter, kept byte-identical in the four repositories. No test here uses it yet. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MjAMq3jnoveX5dcvLGhNQw
…renders if-no-files-found codeql.yml builds a whole reactor, and java-llama.cpp's reactor carries a module with a Java floor above .java-version (llama-ffm, Java 22 through maven-toolchains-plugin), so the shared workflow installs JDK 25 before the .java-version one -- harmless here, where no such module exists. The shared test helper's upload() also renders `if-no-files-found`, which java-llama.cpp's natives check now demands of its signed re-uploads. Both files are kept byte-identical in the four repositories. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01MjAMq3jnoveX5dcvLGhNQw
bernardladenthin
had a problem deploying
to
startgate
October 15, 2026 21:01 — with 
GitHub Actions
Error
GitHub Actions
Error
bernardladenthin
had a problem deploying
to
maven-central
October 15, 2026 21:01 — with
GitHub Actions
Failure
GitHub Actions
Failure
bernardladenthin
had a problem deploying
to
maven-central
October 15, 2026 21:01 — with
GitHub Actions
Failure
GitHub Actions
Failure
This branch had an error being deployed
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
.github/shared-files.sha256: everyuses:pinned to a commit SHA;codeql.ymlinstalls a second JDK (25) before the.java-versionone (java-llama.cpp's reactor now holdsllama-ffm, Java 22+; here the extra JDK is harmless); the buildcheck test helper'supload()rendersoverwrite/if-no-files-found;versions.POMSnamesllama-ffm/pom.xml.net.ladenthin:llamaandllama-platformpinned to 6.0.0: java-llama.cpp renumbered its next release from 5.2.0 to 6.0.0 (its modular natives are a breaking change). That version is not on Maven Central yet; the pin resolves once the 6.0.0 snapshot or release is published, exactly as the 5.2.0 pin did before.Test plan
python3 -m unittest discover -s .github/buildcheck/tests -t .github(144 tests),check-shared-files.pyconsistent with the sibling branchesllama6.0.0 pin needs the published artifact)Related issues / PRs
Part of the cross-repo sync behind java-llama.cpp's "Delivery roadmap" PR; the same shared files land in BitcoinAddressFinder and streambuffer.
shared-fileswarns until all four have merged.Checklist
CONTRIBUTING.mdandCODE_OF_CONDUCT.md🤖 Generated with Claude Code
https://claude.ai/code/session_01MjAMq3jnoveX5dcvLGhNQw
Generated by Claude Code