Skip to content

Instantly share code, notes, and snippets.

@jaceju
Created August 14, 2026 03:34
Show Gist options
  • Select an option

  • Save jaceju/6f274157d31536f10cf7592451175010 to your computer and use it in GitHub Desktop.

Select an option

Save jaceju/6f274157d31536f10cf7592451175010 to your computer and use it in GitHub Desktop.
GitHub Actions version
原本常見版本 支援 Node.js 24 的版本 建議替換 備註
actions/checkout@v4 v5 起;目前也有 v6 actions/checkout@v5@v6 v5 明確改為 Node 24;v6 另有 credentials 儲存位置調整,若 workflow 有 git push/自訂 credential 行為,升級前要測。(GitHub)
actions/setup-node@v4 v5 actions/setup-node@v5 v5 改為 Node 24,且有 caching 預設行為變更;敏感 workflow 可加 package-manager-cache: false。(GitHub)
actions/cache@v4 v5 actions/cache@v5 Marketplace 註明 actions/cache@v5 runs on Node.js 24,runner 需 2.327.1+。(GitHub)
actions/upload-artifact@v4 v6 actions/upload-artifact@v6 v6 改為 Node 24,runner 需 2.327.1+。(GitHub)
actions/download-artifact@v5 / @v6 v7 actions/download-artifact@v7 v7 預設 Node 24;v6 曾有初步支援但預設仍可能是 Node 20。(Zamar: Research)
actions/setup-python@v5 v6 actions/setup-python@v6 v6 升級到 Node 24,runner 需 2.327.1+。(GitHub)
actions/setup-java@v4 v5 actions/setup-java@v5 v5 升級到 Node 24,runner 需 2.327.1+。(GitHub)
actions/setup-go@v5 v6 actions/setup-go@v6 v6 升級 Node runtime 到 Node 24,並有 Go toolchain / cache key 相關 breaking changes。(GitHub)
actions/setup-dotnet@v4 v5 actions/setup-dotnet@v5 官方 repo / release 已有 v5.x;若你的 workflow 目前是 v4,可列入升級候選。(GitHub)
actions/github-script@v7 v8 actions/github-script@v8 v8 明確改為 Node 24;script 本身會受到 Node 20 → 24 的 runtime 差異影響。(GitHub)
github/codeql-action/*@v3 v4 github/codeql-action/init@v4analyze@v4upload-sarif@v4 GitHub 公告 CodeQL Action v4 使用 Node.js 24;v3 將隨 GHES 3.19 時程棄用。(The GitHub Blog)
docker/build-push-action@v6 v7 docker/build-push-action@v7 v7 release note 寫明 Node 24 as default runtime,runner 需 2.327.1+。(GitHub)
docker/login-action@v3 v4 docker/login-action@v4 Marketplace 目前顯示 latest 為 v4.1.0。(GitHub)
azure/login@v2 v3 azure/login@v3 v3 release note 寫明從 Node 20 升到 Node 24。(GitHub)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment