Skip to content

chore: upgrade GitHub Actions to latest versions#103

Open
dotjoshrc wants to merge 2 commits into
mainfrom
chore/upgrades
Open

chore: upgrade GitHub Actions to latest versions#103
dotjoshrc wants to merge 2 commits into
mainfrom
chore/upgrades

Conversation

@dotjoshrc

Copy link
Copy Markdown
Contributor

Upgrades all GitHub Actions used across the workflows to their latest releases, keeping SHA pins with matching version comments.

Action Before After
actions/checkout v6.0.2 (v4.2.2 in scorecard) v7.0.1
actions/setup-node 6.4.0 7.0.0
actions/upload-artifact v4.6.1 (scorecard) v7.0.1
ruby/setup-ruby v1.306.0 v1.321.0
super-linter/super-linter/slim v8.6.0 v8.7.0
ossf/scorecard-action v2.4.1 v2.4.3
github/codeql-action/upload-sarif v4.37.1 v4.37.3

licensee/setup-licensed was already on the latest release (v1.3.2).

Breaking-change notes

  • The major bumps (checkout v6→v7, setup-node v6→v7, upload-artifact →v7) all migrate to the Node.js 24 runtime. This requires Actions Runner ≥ 2.327.1 on self-hosted runners; all workflows here use GitHub-hosted ubuntu-latest, so no impact.
  • checkout v7 blocks checking out fork PRs under pull_request_target/workflow_run — no workflow here uses those triggers.
  • No other behavioral changes affect these workflows.

- actions/checkout v6.0.2 (v4.2.2 in scorecard) -> v7.0.1
- actions/setup-node 6.4.0 -> 7.0.0
- actions/upload-artifact v4.6.1 -> v7.0.1 (scorecard)
- ruby/setup-ruby v1.306.0 -> v1.321.0
- super-linter/super-linter v8.6.0 -> v8.7.0
- ossf/scorecard-action v2.4.1 -> v2.4.3
- github/codeql-action v4.37.1 -> v4.37.3
@dotjoshrc
dotjoshrc requested a review from a team as a code owner July 23, 2026 01:02
zizmor's ref-version-mismatch audit compares pin comments against the
actual git tag (v7.0.x). The bare "# 7.0.x" comments counted as
mismatches; align them with the v-prefixed style used elsewhere.
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