-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
Comparing changes
Open a pull request
base repository: mudler/LocalAI
base: v4.2.2
head repository: mudler/LocalAI
compare: v4.2.3
- 5 commits
- 5 files changed
- 3 contributors
Commits on May 12, 2026
-
ci(merge): source per-arch digests from ci-cache, not local-ai-backends
Follow-up to PR #9781. v4.2.2 (run 25745181433) showed the keepalive anchor in ci-cache wasn't enough on its own: 19 of 37 multiarch merges still failed with "manifest not found" for the same digests we'd just anchored. Quay's manifest GC is per-repository. The anchor tag in ci-cache protects the manifest copy that lives in ci-cache, but the same digest in local-ai-backends is independently tracked and gets reaped because nothing in local-ai-backends references it (push-by-digest=true leaves it untagged). The merge then asks `local-ai-backends@sha256:<digest>` and quay correctly says "not found" in that repo, even though `ci-cache@sha256:<digest>` is alive and well. Empirical confirmation against a live failed digest from v4.2.2: $ docker buildx imagetools inspect quay.io/go-skynet/ci-cache@sha256:05377fe6... Name: quay.io/go-skynet/ci-cache@sha256:05377fe6... MediaType: application/vnd.docker.distribution.manifest.v2+json $ docker buildx imagetools inspect quay.io/go-skynet/local-ai-backends@sha256:05377fe6... ERROR: ... not found Switch the source of the quay merge step to ci-cache. The blobs the manifest references are already accessible from local-ai-backends (verified via direct registry HEAD: HTTP 200 from both repos — the original push cross-mounted blobs at content-addressable storage time and they outlive the per-repo manifest GC). buildx imagetools create republishes the manifest into local-ai-backends, then writes the user-facing manifest list pointing at it. End state is self-contained: the published manifest list references child manifests by digest only, no embedded reference to ci-cache. Dockerhub merge step is unchanged. Dockerhub's GC isn't aggressive enough to reap untagged manifests at the timescales we operate on (verified: localai/localai-backends@<same digest> still resolves cleanly after >24h). Assisted-by: Claude:claude-opus-4-7 Signed-off-by: Ettore Di Giacinto <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 8521af1 - Browse repository at this point
Copy the full SHA 8521af1View commit details -
chore: ⬆️ Update ggml-org/whisper.cpp to `338cce1e58133261753243802a0…
…e7a430118866d` (#9793) ⬆️ Update ggml-org/whisper.cpp Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: mudler <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 602866a - Browse repository at this point
Copy the full SHA 602866aView commit details -
chore: ⬆️ Update antirez/ds4 to `f8b4ed635d559b3a5b44bf2df6a77e21b3e9…
…178f` (#9794) ⬆️ Update antirez/ds4 Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: mudler <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 0b81e36 - Browse repository at this point
Copy the full SHA 0b81e36View commit details -
docs: ⬆️ update docs version mudler/LocalAI (#9792)
⬆️ Update docs version mudler/LocalAI Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: mudler <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for ad0ab37 - Browse repository at this point
Copy the full SHA ad0ab37View commit details -
chore: ⬆️ Update ikawrakow/ik_llama.cpp to `f9a93c37e2fc021760c3c1aa9…
…9cf74c73b7591a7` (#9795) ⬆️ Update ikawrakow/ik_llama.cpp Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: mudler <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 957619a - Browse repository at this point
Copy the full SHA 957619aView commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v4.2.2...v4.2.3