git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH] CI: bump actions/checkout from 4 to 5 for rust-analysis job

From
Junio C Hamano <gitster@pobox.com>
Date
Apr 13, 2026, 18:24 UTC
Message-ID
<xmqqfr4yhg5v.fsf@gitster.g>

GitHub Actions started complaining about use of Node.js 20 and I was wondering why only one job uses actions/checkout@v4, while everybody else already uses actions/checkout@v5. It turns out that it is a semantic mismerge between e75cd059 (ci: check formatting of our Rust code, 2025-10-15) that added a new use of actions/checkout@v4 that happened very close to another change 63541ed9 (build(deps): bump actions/checkout from 4 to 5, 2025-10-16) that updated all uses of actions/checkout@v4 to use actions/checkout@v5.

Update the leftover and the last use of actions/checkout@v4 to use actions/checkout@v5 to help ourselves to move away from Node.js 20.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
 .github/workflows/main.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
diff --git c/.github/workflows/main.yml w/.github/workflows/main.yml
index 826f2f5d3a..6f3d94e3a6 100644
--- c/.github/workflows/main.yml
+++ w/.github/workflows/main.yml
@@ -480,7 +480,7 @@ jobs:
       group: rust-analysis-${{ github.ref }}
       cancel-in-progress: ${{ needs.ci-config.outputs.skip_concurrent == 'yes' }}
     steps:
-    - uses: actions/checkout@v4
+    - uses: actions/checkout@v5
     - run: ci/install-dependencies.sh
     - run: ci/run-rust-checks.sh
   sparse:
Message 1 of 1 in “CI: bump actions/checkout from 4 to 5 for rust-analysis job”
  1. CI: bump actions/checkout from 4 to 5 for rust-analysis jobJunio C Hamano, Apr 13, 2026

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.