Skip to content

Conversation

@pgoslatara
Copy link

Make sure to read the contributing guidelines before submitting a PR

  • Updated actions/checkout from v4 to v6 in .github/workflows/build.yml
  • Updated actions/checkout from v4 to v6 in .github/workflows/server.yml
  • Updated actions/checkout from v4 to v6 in .github/workflows/python-type-check.yml
  • Updated actions/checkout from v4 to v6 in .github/workflows/python-lint.yml
  • Updated actions/labeler from v5 to v6 in .github/workflows/labeler.yml
  • Updated actions/stale from v5 to v10 in .github/workflows/close-issue.yml
  • Updated actions/checkout from v4 to v6 in .github/workflows/python-check-requirements.yml
  • Updated actions/upload-artifact from v4 to v6 in .github/workflows/build.yml
  • Updated docker/login-action from v2 to v3 in .github/workflows/docker.yml
  • Updated actions/checkout from v4 to v6 in .github/workflows/update-ops-docs.yml
  • Updated actions/checkout from v4 to v6 in .github/workflows/build-cmake-pkg.yml
  • Updated actions/checkout from v4 to v6 in .github/workflows/labeler.yml
  • Updated actions/cache from v4 to v5 in .github/workflows/build.yml
  • Updated actions/download-artifact from v4 to v7 in .github/workflows/build.yml
  • Updated actions/checkout from v4 to v6 in .github/workflows/python-lint.yml
  • Updated actions/checkout from v4 to v6 in .github/workflows/python-check-requirements.yml
  • Updated actions/cache from v4 to v5 in .github/workflows/release.yml
  • Updated actions/checkout from v4 to v6 in .github/workflows/build-linux-cross.yml
  • Updated actions/checkout from v4 to v6 in .github/workflows/editorconfig.yml
  • Updated actions/setup-python from v5 to v6 in .github/workflows/gguf-publish.yml
  • Updated actions/checkout from v4 to v6 in .github/workflows/docker.yml
  • Updated actions/checkout from v4 to v6 in .github/workflows/server-webui.yml
  • Updated actions/upload-artifact from v4 to v6 in .github/workflows/release.yml
  • Updated actions/cache from v4 to v5 in .github/workflows/build-linux-cross.yml
  • Updated actions/cache from v4 to v5 in .github/workflows/build-cache.yml
  • Updated actions/checkout from v4 to v6 in .github/workflows/server-webui.yml
  • Updated actions/setup-java from v3 to v5 in .github/workflows/build.yml
  • Updated actions/checkout from v4 to v6 in .github/workflows/python-type-check.yml
  • Updated actions/github-script from v6 to v8 in .github/workflows/winget.yml
  • Updated actions/setup-python from v4 to v6 in .github/workflows/check-vendor.yml
  • Updated actions/checkout from v4 to v6 in .github/workflows/copilot-setup-steps.yml
  • Updated actions/checkout from v4 to v6 in .github/workflows/update-ops-docs.yml
  • Updated actions/setup-node from v4 to v6 in .github/workflows/server-webui.yml

These changes will be tested in the CI pipeline of the pull request.

@github-actions github-actions bot added the devops improvements to build systems and github actions label Jan 19, 2026
@pgoslatara pgoslatara marked this pull request as ready for review January 19, 2026 16:37
@pgoslatara pgoslatara requested a review from CISC as a code owner January 19, 2026 16:37
@CISC
Copy link
Collaborator

CISC commented Jan 19, 2026

I'm generally ok with this, however I'd like you to at least test the following workflows on your fork first:

  • build
  • docker
  • labeler (mentions breaking changes to config)
  • release
  • server

Some of the runners will not start due to being self-hosted, which is ok, but brings me to the next point; actions/cache@v5 requires Actions Runner to be at least version 2.327.1. @alitariq4589 @ggerganov @taronaeo do we fullfill that requirement?

@alitariq4589
Copy link
Contributor

actions/cache@v5 requires Actions Runner to be at least version 2.327.1. @alitariq4589 @ggerganov @taronaeo do we fullfill that requirement?

In RISC-V builds, all the runners are using github version 2.329.0 as of now. So I think we are good for RISC-V runners.

image

@ggerganov
Copy link
Member

The 4 ggml-ci runners are all 2.331.0:

image

@taronaeo
Copy link
Collaborator

taronaeo commented Jan 19, 2026

@taronaeo do we fullfill that requirement?

All good for s390x as well :)

image

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

Labels

devops improvements to build systems and github actions

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants