b10470

ggml-org/llama.cppb10470Aug 17, 2026by github-actions[bot]same day as b10456

What changed since b10456

low risk

CI-only change: release workflow now pushes the b<number> tag explicitly; no runtime or API changes.

Improvements

  • Release workflow now creates and pushes the lightweight b<number> git tag with the deploy key before invoking the GitHub Releases API.
  • Tag creation step is idempotent, skipping create/push when the tag already exists on re-runs.
  • Release tags no longer depend on the Releases API creating them as a side effect, making them reliably available to downstream workflows.

Upgrade notes

This delta touches only the project's GitHub Actions release pipeline; the compiled binaries and CLI/API surface are functionally identical to b10456. No config, model, or migration steps are required — upgrading is a straight artifact swap. The SYCL quantized-copy performance gains from b10456 remain in place.

Analyzed Oct 24, 2026

Upgrading?

Release notes summary

This release updates the CI/CD pipeline to explicitly push the release tag using git tag before creating the release via the GitHub API, ensuring the tag is available for workflows.

Key Highlights

  • Updated CI/CD to explicitly push release tags
  • Added step to create and push b<number> tag before release creation
  • Made the step idempotent

New Features

  • CI/CD release tagging improvement

Release Notes (excerpt)

<details open> ci : push release tag explicitly in release.yml (#27261) Add a "Create and push git tag" step to the release job, right before the "Create release" step. The tag is created with git tag and pushed with the deploy key already configured by the Clone step, instead of relying on the Releases API (action-create-release) to create it as a side effect. The tag is lightweight, matching all existing b<number> release tags.…

Published by ggml-org on GitHub.

Read the full release notes

Related Repositories