Skip to content

Upgrade GitHub Actions for Node 24 compatibility#346

Open
salmanmkc wants to merge 2 commits intogoogle:mainfrom
salmanmkc:upgrade-github-actions-node24
Open

Upgrade GitHub Actions for Node 24 compatibility#346
salmanmkc wants to merge 2 commits intogoogle:mainfrom
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 check-pr-up-to-date.yaml, ci.yaml, publish.yml, validate-community-providers.yaml, zenodo-publish.yml
actions/github-script v7 v8 Release auto-update-pr.yaml, check-infrastructure-changes.yml, check-linked-issue.yml, check-pr-size.yml, check-pr-up-to-date.yaml, ci.yaml, revalidate-pr.yml, validate_pr_template.yaml
actions/setup-python v5 v6 Release ci.yaml, publish.yml, validate-community-providers.yaml, zenodo-publish.yml

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>
@github-actions
Copy link
Copy Markdown

github-actions bot commented Feb 9, 2026

Infrastructure File Protection

This PR modifies protected infrastructure files:

  • .github/workflows/auto-update-pr.yaml (2 changes)
  • .github/workflows/check-infrastructure-changes.yml (2 changes)
  • .github/workflows/check-linked-issue.yml (2 changes)
  • .github/workflows/check-pr-size.yml (4 changes)
  • .github/workflows/check-pr-up-to-date.yaml (4 changes)
  • .github/workflows/ci.yaml (36 changes)
  • .github/workflows/publish.yml (4 changes)
  • .github/workflows/revalidate-pr.yml (10 changes)
  • .github/workflows/validate-community-providers.yaml (4 changes)
  • .github/workflows/validate_pr_template.yaml (2 changes)
  • .github/workflows/zenodo-publish.yml (4 changes)

Only repository maintainers are allowed to modify infrastructure files (including .github/, build configuration, and repository documentation).

Note: If these are only formatting changes, please:

  1. Revert changes to .github/ files
  2. Use ./autoformat.sh to format only source code directories
  3. Avoid running formatters on infrastructure files

If structural changes are necessary:

  1. Open an issue describing the needed infrastructure changes
  2. A maintainer will review and implement the changes if approved

For more information, see our Contributing Guidelines.

@github-actions
Copy link
Copy Markdown

github-actions bot commented Feb 9, 2026

No linked issues found. Please link an issue in your pull request description or title.

Per our Contributing Guidelines, all PRs must:

  • Reference an issue with one of:
    • Closing keywords: Fixes #123, Closes #123, Resolves #123 (auto-closes on merge in the same repository)
    • Reference keywords: Related to #123, Refs #123, Part of #123, See #123 (links without closing)
  • The linked issue should have 5+ 👍 reactions from unique users (excluding bots and the PR author)
  • Include discussion demonstrating the importance of the change

You can also use cross-repo references like owner/repo#123 or full URLs.

@github-actions github-actions bot added the size/S Pull request with 50-150 lines changed label Feb 9, 2026
@github-actions
Copy link
Copy Markdown

⚠️ Branch Update Required

Your branch is 1 commits behind main. Please update your branch to ensure CI checks run with the latest code:

git fetch origin main
git merge origin/main
git push

Note: Enable "Allow edits by maintainers" to allow automatic updates.

3 similar comments
@github-actions
Copy link
Copy Markdown

github-actions bot commented Mar 5, 2026

⚠️ Branch Update Required

Your branch is 1 commits behind main. Please update your branch to ensure CI checks run with the latest code:

git fetch origin main
git merge origin/main
git push

Note: Enable "Allow edits by maintainers" to allow automatic updates.

@github-actions
Copy link
Copy Markdown

⚠️ Branch Update Required

Your branch is 1 commits behind main. Please update your branch to ensure CI checks run with the latest code:

git fetch origin main
git merge origin/main
git push

Note: Enable "Allow edits by maintainers" to allow automatic updates.

@github-actions
Copy link
Copy Markdown

⚠️ Branch Update Required

Your branch is 1 commits behind main. Please update your branch to ensure CI checks run with the latest code:

git fetch origin main
git merge origin/main
git push

Note: Enable "Allow edits by maintainers" to allow automatic updates.

@github-actions
Copy link
Copy Markdown

Infrastructure File Protection

This PR modifies protected infrastructure files:

  • .github/workflows/auto-update-pr.yaml (2 changes)
  • .github/workflows/check-infrastructure-changes.yml (2 changes)
  • .github/workflows/check-linked-issue.yml (2 changes)
  • .github/workflows/check-pr-size.yml (4 changes)
  • .github/workflows/check-pr-up-to-date.yaml (4 changes)
  • .github/workflows/ci.yaml (36 changes)
  • .github/workflows/publish.yml (4 changes)
  • .github/workflows/revalidate-pr.yml (10 changes)
  • .github/workflows/validate-community-providers.yaml (4 changes)
  • .github/workflows/validate_pr_template.yaml (2 changes)
  • .github/workflows/zenodo-publish.yml (4 changes)

Only repository maintainers are allowed to modify infrastructure files (including .github/, build configuration, and repository documentation).

Note: If these are only formatting changes, please:

  1. Revert changes to .github/ files
  2. Use ./autoformat.sh to format only source code directories
  3. Avoid running formatters on infrastructure files

If structural changes are necessary:

  1. Open an issue describing the needed infrastructure changes
  2. A maintainer will review and implement the changes if approved

For more information, see our Contributing Guidelines.

@github-actions
Copy link
Copy Markdown

⚠️ Branch Update Required

Your branch is 6 commits behind main. Please update your branch to ensure CI checks run with the latest code:

git fetch origin main
git merge origin/main
git push

Note: Enable "Allow edits by maintainers" to allow automatic updates.

1 similar comment
@github-actions
Copy link
Copy Markdown

github-actions bot commented Apr 2, 2026

⚠️ Branch Update Required

Your branch is 6 commits behind main. Please update your branch to ensure CI checks run with the latest code:

git fetch origin main
git merge origin/main
git push

Note: Enable "Allow edits by maintainers" to allow automatic updates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size/S Pull request with 50-150 lines changed

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant