Skip to content

Upgrade GitHub Actions for Node 24 compatibility#558

Open
salmanmkc wants to merge 1 commit intouber:masterfrom
salmanmkc:upgrade-github-actions-node24
Open

Upgrade GitHub Actions for Node 24 compatibility#558
salmanmkc wants to merge 1 commit intouber:masterfrom
salmanmkc:upgrade-github-actions-node24

Conversation

@salmanmkc
Copy link
Copy Markdown

Summary

Upgrade GitHub Actions to their latest versions to ensure compatibility with Node 24, as Node 20 will reach end-of-life in April 2026.

Changes

Action Old Version(s) New Version Release Files
actions/checkout v4 v6 Release build-and-test.yaml, vulnerability-check.yaml
actions/setup-go v5 v6 Release build-and-test.yaml
actions/setup-python v5 v6 Release build-and-test.yaml

Context

Per GitHub's announcement, Node 20 is being deprecated and runners will begin using Node 24 by default starting March 4th, 2026.

Why this matters

  • Node 20 EOL: April 2026
  • Node 24 default: March 4th, 2026
  • Action: Update to latest action versions that support Node 24

Security Note

Actions that were previously pinned to commit SHAs remain pinned to SHAs (updated to the latest release SHA) to maintain the security benefits of immutable references.

Testing

These changes only affect CI/CD workflow configurations and should not impact application functionality. The workflows should be tested by running them on a branch before merging.

Signed-off-by: Salman Muin Kayser Chishti <13schishti@gmail.com>
Copilot AI review requested due to automatic review settings February 7, 2026 23:32
@CLAassistant
Copy link
Copy Markdown

CLAassistant commented Feb 7, 2026

CLA assistant check
All committers have signed the CLA.

Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

Updates GitHub Actions workflow dependencies to newer major versions to ensure runner compatibility as GitHub Actions transitions from Node 20 to Node 24.

Changes:

  • Upgraded actions/checkout from v4 to v6 across workflows.
  • Upgraded actions/setup-go from v5 to v6 in build jobs.
  • Upgraded actions/setup-python from v5 to v6 for integration tests.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File Description
.github/workflows/build-and-test.yaml Bumps checkout, setup-go, and setup-python major versions used by lint/build/test jobs.
.github/workflows/vulnerability-check.yaml Bumps checkout major version used by Trivy scan/report jobs.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment on lines +17 to +18
- uses: actions/checkout@v6
- uses: actions/setup-go@v6
Copy link

Copilot AI Feb 7, 2026

Choose a reason for hiding this comment

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

The PR description says actions are pinned to immutable commit SHAs, but this workflow references major tags (e.g., actions/checkout@v6, actions/setup-go@v6). Either update the workflows to pin these actions to specific release SHAs, or adjust the PR description/security note to match what’s actually being used.

Copilot uses AI. Check for mistakes.
Comment on lines 12 to 20
trivy_scan:
name: Trivy Vulnerability Scan
runs-on: ubuntu-latest
if: github.event_name == 'pull_request'

steps:
- name: Checkout Repository
uses: actions/checkout@v4
uses: actions/checkout@v6

Copy link

Copilot AI Feb 7, 2026

Choose a reason for hiding this comment

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

trivy_report explicitly sets minimal job permissions, but trivy_scan does not. To keep least-privilege consistent (and avoid relying on repo default permissions), add an explicit permissions: block for trivy_scan (at least contents: read for checkout).

Copilot uses AI. Check for mistakes.
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.

4 participants