Skip to content

ci: bump GitHub Actions to latest majors (checkout v7, setup-dotnet v6, artifact v7/v8, setup-python v7) - #630

Merged
Nucs merged 1 commit into
masterfrom
ci/bump-action-versions
Sep 7, 2026
Merged

ci: bump GitHub Actions to latest majors (checkout v7, setup-dotnet v6, artifact v7/v8, setup-python v7)#630
Nucs merged 1 commit into
masterfrom
ci/bump-action-versions

Conversation

@Nucs

@Nucs Nucs commented Sep 6, 2026

Copy link
Copy Markdown
Member

Summary

Bumps the five GitHub Actions that were behind their latest published major, across all four workflow files (benchmark.yml, build-and-release.yml, docs.yml, fuzz-soak.yml).

Action Before After
actions/checkout v5 v7
actions/download-artifact v7 v8
actions/upload-artifact v6 v7
actions/setup-python v6 v7
actions/setup-dotnet v5 v6

Already at their current-latest majors, left unchanged: softprops/action-gh-release@v3, actions/configure-pages@v6, actions/deploy-pages@v5, actions/upload-pages-artifact@v5.

Scope

Why the branch's CI is the gate

These are major-version bumps. The upload-artifact / download-artifact pair in particular must round-trip (those actions changed artifact semantics across the v3→v4 boundary; upload@v7 + download@v8 are the current compatible pair). Let this branch's build / test / interop / package-consumer-smoke jobs prove nothing broke before merging. This PR publishes nothing (release jobs are tag-only).

Updates the five action pins that were behind their latest published major,
across all four workflow files (benchmark.yml, build-and-release.yml, docs.yml,
fuzz-soak.yml):

  actions/checkout          v5 -> v7   (was two majors behind)
  actions/download-artifact v7 -> v8
  actions/upload-artifact   v6 -> v7
  actions/setup-python      v6 -> v7
  actions/setup-dotnet      v5 -> v6

Left at their already-current majors (unchanged): softprops/action-gh-release@v3,
actions/configure-pages@v6, actions/deploy-pages@v5, actions/upload-pages-artifact@v5.

These are major-version bumps, so the branch's CI is the gate — in particular the
upload-artifact / download-artifact pair must round-trip (those actions changed
artifact semantics across the v3->v4 boundary; upload@v7 and download@v8 are the
current compatible pair). No workflow logic changed — only the `uses:` pins.
@Nucs
Nucs merged commit 4c5b1ed into master Sep 7, 2026
16 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant