Skip to content

[8.4] Bump GitHub Actions to Node 24 compatible versions [MOD-15112] #948

Open
github-actions[bot] wants to merge 1 commit into8.4from
backport-947-to-8.4
Open

[8.4] Bump GitHub Actions to Node 24 compatible versions [MOD-15112] #948
github-actions[bot] wants to merge 1 commit into8.4from
backport-947-to-8.4

Conversation

@github-actions
Copy link
Copy Markdown

@github-actions github-actions Bot commented May 4, 2026

Description

Backport of #947 to 8.4.


Note

Medium Risk
Moderate risk because it updates multiple CI workflows’ third-party actions (runner provisioning, CodeQL, Codecov, artifacts, Slack), which can change behavior and potentially break builds or notifications.

Overview
Updates GitHub Actions workflows to Node 24–compatible action versions across CI, coverage, ARM/benchmark self-hosted EC2 runner provisioning, CodeQL, release drafting, and backport automation.

Also updates nightly failure Slack notifications to slackapi/slack-github-action@v3, switching from SLACK_WEBHOOK_URL env usage to explicit webhook/webhook-type inputs.

Reviewed by Cursor Bugbot for commit 12a1622. Bugbot is set up for automated code reviews on this repo. Configure here.

[MOD-15112] Bump GitHub Actions to Node 24 compatible versions

Migrate all JavaScript-based GitHub Actions to versions running on the
Node 24 runtime ahead of the June 2, 2026 Node 20 deprecation.

- actions/checkout v4 -> v6
- actions/setup-python v5 -> v6
- actions/upload-artifact v4 -> v7
- aws-actions/configure-aws-credentials v4 -> v6
- machulav/ec2-github-runner v2.4.2 -> v2.6.1
- codecov/codecov-action v4 -> v6
- github/codeql-action/* v3 -> v4
- korthout/backport-action v3 -> v4
- release-drafter/release-drafter v6 -> v7
- slackapi/slack-github-action v1 -> v3 (input-based webhook config)

(cherry picked from commit 369f14f)
@GuyAv46 GuyAv46 marked this pull request as draft May 4, 2026 14:31
@GuyAv46 GuyAv46 marked this pull request as ready for review May 4, 2026 14:31
@GuyAv46 GuyAv46 requested a review from dor-forer May 4, 2026 14:31
@jit-ci
Copy link
Copy Markdown

jit-ci Bot commented May 4, 2026

🛡️ Jit Security Scan Results

CRITICAL HIGH MEDIUM

✅ No security findings were detected in this PR


Security scan by Jit

Copy link
Copy Markdown

@cursor cursor Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 2 potential issues.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 12a1622. Configure here.

Comment thread .github/workflows/arm.yml
- name: Start EC2 runner
id: start-ec2-runner
uses: machulav/ec2-github-runner@v2.4.2
uses: machulav/ec2-github-runner@v2.6.1
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Non-existent action version referenced for EC2 runner

High Severity

machulav/ec2-github-runner@v2.6.1 does not appear to exist as a published tag or release. The latest available version is v2.5.2. This will cause all workflows using this action (arm, benchmark-runner, and coverage, including their stop-runner jobs) to fail immediately when GitHub Actions attempts to download the action.

Additional Locations (2)
Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 12a1622. Configure here.

steps:
# Drafts your next Release notes as Pull Requests are merged into "master"
- uses: release-drafter/release-drafter@v6
- uses: release-drafter/release-drafter@v7
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Stale GITHUB_TOKEN env var ignored by release-drafter v7

Low Severity

release-drafter/release-drafter@v7 replaced the GITHUB_TOKEN environment variable with a token input (which defaults to ${{ github.token }}). The env: GITHUB_TOKEN block on this step is now dead code — the action ignores it. The workflow still functions because the default token value is equivalent, but the env var is misleading.

Fix in Cursor Fix in Web

Reviewed by Cursor Bugbot for commit 12a1622. Configure here.

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