Skip to content

ci : allow make-release to target a specific commit - #27234

Merged
ggerganov merged 3 commits into
masterfrom
gg/ci-make-release-add-commit
Aug 17, 2026
Merged

ci : allow make-release to target a specific commit#27234
ggerganov merged 3 commits into
masterfrom
gg/ci-make-release-add-commit

Conversation

@ggerganov

@ggerganov ggerganov commented Aug 17, 2026 •
edited
Loading

Copy link
Copy Markdown
Member

Overview

The make-release workflow now accepts an optional commit input. When set,
that commit is checked out (instead of the tip of the selected branch) and
the release checks run against it:

  • the release branch is the one selected in the "Run workflow" dialog (github.ref_name, by default master):

    image

  • make-release-checks.sh verifies that the commit belongs to that branch and is
    not older than 3 days from the branch HEAD (same dry-run semantics as the other checks)

  • the CI check now scans the latest 100 release.yml runs, so that a commit
    behind the tip is still matched correctly

  • no need to manually check release.yml has completed - the Github ruleset already supports this:

    image

Requirements

@github-actions github-actions Bot added documentation Improvements or additions to documentation devops improvements to build systems and github actions labels Aug 17, 2026
@ggerganov
ci : allow make-release to target a specific commit
ce62f63 
The make-release workflow now accepts an optional 'commit' input. When
set, that commit is checked out and the release checks verify that it
belongs to the branch selected in the "Run workflow" dialog and is not
older than 3 days from the branch tip. The check is part of
make-release-checks.sh (driven by the RELEASE_BRANCH env), so it follows
the same dry-run semantics as the other checks.

Assisted-by: pi:llama.cpp/Qwen3.8-27B
@ggerganov
cont : scan latest 100 relase workflow runs
24e5462
@ggerganov
ggerganov force-pushed the gg/ci-make-release-add-commit branch from e94f5ef to 24e5462 Compare August 17, 2026 08:35
@ggerganov
ggerganov marked this pull request as ready for review August 17, 2026 08:40
@ggerganov
ggerganov requested a review from a team as a code owner August 17, 2026 08:40
@ggerganov
ggerganov merged commit 7c35571 into master Aug 17, 2026
3 checks passed
@ggerganov
ggerganov deleted the gg/ci-make-release-add-commit branch August 17, 2026 08:52
@ggerganov ggerganov mentioned this pull request Aug 17, 2026
Merged
gabe-l-hart added a commit to gabe-l-hart/llama.cpp that referenced this pull request Aug 17, 2026
@gabe-l-hart
Merge remote-tracking branch 'origin/master' into GraniteSWAForCausalLM
283c4ec 
* origin/master: (86 commits)
ui: enforce alphabetical enum member ordering (ggml-org#27272)
ui: Refactor Built-In Tools naming (Server/Browser) (ggml-org#27271)
ci: more optimizations (ggml-org#26983)
doc: document MCP stdio servers and CORS defaults in the server README [no release] [no ci] (ggml-org#26847)
server: save processed mtmd chunks as placeholder (ggml-org#27278)
mtmd: use sha256 for input hashing (ggml-org#27274)
vocab : support integer tokenizer scores (ggml-org#27260)
mtmd : skip thumbnail for non-tiled LFM2 images (ggml-org#27246)
cuda : skip UMA override for HIP builds (ggml-org#27083)
vendor: move hash to vendor (ggml-org#27262)
ci : push release tag explicitly in release.yml (ggml-org#27261)
ui: move get_datetime tool to frontend (ggml-org#27255)
ci : reduce builds in build-xcframework.sh (ggml-org#27252)
model: support speculators-format checkpoints for DSpark (ggml-org#26275)
ui: add browser get_info tool (ggml-org#27251)
ci : restore release.yml check during make-release.yml (ggml-org#27247)
mtmd: harden preprocessor_granite (ggml-org#27235)
ci : allow make-release to target a specific commit (ggml-org#27234)
ci : make release workflows use a deploy key (ggml-org#27229)
convert: add @ModelBase.example (ggml-org#27208)
...
brittlewis12 pushed a commit to brittlewis12/llama.cpp that referenced this pull request Aug 17, 2026
@ggerganov @brittlewis12
ci : allow make-release to target a specific commit (ggml-org#27234)
8612d81 
* ci : allow make-release to target a specific commit

The make-release workflow now accepts an optional 'commit' input. When
set, that commit is checked out and the release checks verify that it
belongs to the branch selected in the "Run workflow" dialog and is not
older than 3 days from the branch tip. The check is part of
make-release-checks.sh (driven by the RELEASE_BRANCH env), so it follows
the same dry-run semantics as the other checks.

Assisted-by: pi:llama.cpp/Qwen3.8-27B

* cont : scan latest 100 relase workflow runs

* cont : do not check manually for release.yml success
thecodacus pushed a commit to thecodacus/llama.cpp that referenced this pull request Sep 7, 2026
@ggerganov
ci : allow make-release to target a specific commit (ggml-org#27234)
f565706 
* ci : allow make-release to target a specific commit

The make-release workflow now accepts an optional 'commit' input. When
set, that commit is checked out and the release checks verify that it
belongs to the branch selected in the "Run workflow" dialog and is not
older than 3 days from the branch tip. The check is part of
make-release-checks.sh (driven by the RELEASE_BRANCH env), so it follows
the same dry-run semantics as the other checks.

Assisted-by: pi:llama.cpp/Qwen3.8-27B

* cont : scan latest 100 relase workflow runs

* cont : do not check manually for release.yml success
zbrad pushed a commit to zbrad/llama.cpp that referenced this pull request Sep 10, 2026
@ggerganov
ci : allow make-release to target a specific commit (ggml-org#27234)
fc7d789 
* ci : allow make-release to target a specific commit

The make-release workflow now accepts an optional 'commit' input. When
set, that commit is checked out and the release checks verify that it
belongs to the branch selected in the "Run workflow" dialog and is not
older than 3 days from the branch tip. The check is part of
make-release-checks.sh (driven by the RELEASE_BRANCH env), so it follows
the same dry-run semantics as the other checks.

Assisted-by: pi:llama.cpp/Qwen3.8-27B

* cont : scan latest 100 relase workflow runs

* cont : do not check manually for release.yml success
pl752 pushed a commit to pl752/llama.cpp that referenced this pull request Sep 15, 2026
@ggerganov @pl752
ci : allow make-release to target a specific commit (ggml-org#27234)
1c1ca59 
* ci : allow make-release to target a specific commit

The make-release workflow now accepts an optional 'commit' input. When
set, that commit is checked out and the release checks verify that it
belongs to the branch selected in the "Run workflow" dialog and is not
older than 3 days from the branch tip. The check is part of
make-release-checks.sh (driven by the RELEASE_BRANCH env), so it follows
the same dry-run semantics as the other checks.

Assisted-by: pi:llama.cpp/Qwen3.8-27B

* cont : scan latest 100 relase workflow runs

* cont : do not check manually for release.yml success
frostyautumnleaf pushed a commit to frostyautumnleaf/llama.cpp that referenced this pull request Oct 5, 2026
@ggerganov
ci : allow make-release to target a specific commit (ggml-org#27234)
43ea027 
* ci : allow make-release to target a specific commit

The make-release workflow now accepts an optional 'commit' input. When
set, that commit is checked out and the release checks verify that it
belongs to the branch selected in the "Run workflow" dialog and is not
older than 3 days from the branch tip. The check is part of
make-release-checks.sh (driven by the RELEASE_BRANCH env), so it follows
the same dry-run semantics as the other checks.

Assisted-by: pi:llama.cpp/Qwen3.8-27B

* cont : scan latest 100 relase workflow runs

* cont : do not check manually for release.yml success
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@CISC CISC CISC approved these changes

Assignees

No one assigned

Labels

devops improvements to build systems and github actions documentation Improvements or additions to documentation

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@ggerganov @CISC