Skip to content

Bump GitHub Actions workflow dependencies#12

Merged
warunalakshitha merged 1 commit intoballerina-platform:mainfrom
snelusha:chore/fix-action-runners
Mar 23, 2026
Merged

Bump GitHub Actions workflow dependencies#12
warunalakshitha merged 1 commit intoballerina-platform:mainfrom
snelusha:chore/fix-action-runners

Conversation

@snelusha
Copy link
Copy Markdown
Contributor

@snelusha snelusha commented Mar 19, 2026

Purpose

$subject
Resolves #11

Two actions don't yet have a released version with Node 24 support:

Changes Overview

This pull request updates GitHub Actions workflow dependencies across the project's CI/CD pipelines to address the deprecation of Node 20 on GitHub Actions runners and enable Node 24 compatibility.

Workflow Updates

Modified Files

  • .github/workflows/ci.yml
  • .github/workflows/deploy.yml

Dependency Updates

  • actions/checkout: upgraded from v4 to v6
  • actions/setup-go: upgraded from v5 to v6

These version upgrades ensure that the workflow actions are compatible with Node 24 while maintaining all existing configuration settings and build parameters.

Known Limitations

Two upstream GitHub Actions currently lack released versions with Node 24 support and remain unchanged pending upstream releases:

These dependencies will be updated in a follow-up once the upstream projects publish compatible releases.

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Mar 19, 2026

📝 Walkthrough

Walkthrough

Updated GitHub Actions versions in two workflow files: actions/checkout from v4 to v6 and actions/setup-go from v5 to v6 in both .github/workflows/ci.yml and .github/workflows/deploy.yml. No workflow logic or configuration parameters were modified.

Changes

Cohort / File(s) Summary
GitHub Actions Workflow Updates
.github/workflows/ci.yml, .github/workflows/deploy.yml
Updated actions/checkout to v6 and actions/setup-go to v6 to address Node 20 deprecation and maintain compatibility with current GitHub Actions runners.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 Workflows upgraded with care and grace,
New versions now take their place,
Checkout and Go hop ahead with cheer,
Node 24's calling—the future is here! 🚀

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Description check ⚠️ Warning The description partially addresses the template but lacks most required sections (Goals, Approach, User stories, Release note, Documentation, Training, Certification, Marketing, Testing, Security, Samples, Related PRs, Migrations, Test environment, Learning). Expand the description to include key sections from the template such as Goals, Approach, and at minimum indicate N/A for non-applicable sections like Documentation and Training.
✅ Passed checks (4 passed)
Check name Status Explanation
Title check ✅ Passed The title clearly and concisely summarizes the main change: bumping GitHub Actions workflow dependencies.
Linked Issues check ✅ Passed The PR successfully updates actions/checkout and actions/setup-go to v6, addressing the Node 24 compatibility requirement in issue #11.
Out of Scope Changes check ✅ Passed The PR changes are limited to updating two GitHub Actions dependencies in CI/CD workflow files, directly aligned with the Node 24 migration objective.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
📝 Coding Plan
  • Generate coding plan for human review comments

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
.github/workflows/deploy.yml (1)

74-74: ⚠️ Potential issue | 🟠 Major

Update actions/deploy-pages@v4 before Fall 2026 or implement a workaround.

actions/deploy-pages@v4 uses Node 20, which is being phased out by GitHub Actions. Node 20 is deprecated as of September 2025 and will be fully removed from runners in Fall 2026. While workflows will continue to emit deprecation warnings until that date, they will fail after Node 20 is removed.

No v5 version with Node 24 support has been released yet. To unblock this before Fall 2026:

  • Monitor the actions/deploy-pages releases for a v5 update, or
  • Use the temporary workaround: set the environment variable FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true to opt in to Node 24 runtime with v4.

This workflow needs action by Fall 2026.

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In @.github/workflows/deploy.yml at line 74, Update the deploy Pages action
usage to avoid future Node 20 removal by either switching to a v5 when available
or adding the temporary opt-in runtime env; specifically change the action
reference 'uses: actions/deploy-pages@v4' policy by either replacing it with
'actions/deploy-pages@v5' when released or, as a workaround, set the environment
variable FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true in the workflow (e.g., under
the job or step env) so the v4 action runs on Node 24; also add a short comment
referencing monitoring the actions/deploy-pages releases for v5 so the v4
workaround can be removed when v5 is available.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Outside diff comments:
In @.github/workflows/deploy.yml:
- Line 74: Update the deploy Pages action usage to avoid future Node 20 removal
by either switching to a v5 when available or adding the temporary opt-in
runtime env; specifically change the action reference 'uses:
actions/deploy-pages@v4' policy by either replacing it with
'actions/deploy-pages@v5' when released or, as a workaround, set the environment
variable FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true in the workflow (e.g., under
the job or step env) so the v4 action runs on Node 24; also add a short comment
referencing monitoring the actions/deploy-pages releases for v5 so the v4
workaround can be removed when v5 is available.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: fc49bf60-83d4-4b2c-8871-33c090f3ffe4

📥 Commits

Reviewing files that changed from the base of the PR and between 4602662 and a516b31.

📒 Files selected for processing (2)
  • .github/workflows/ci.yml
  • .github/workflows/deploy.yml

Copy link
Copy Markdown
Contributor

@warunalakshitha warunalakshitha left a comment

Choose a reason for hiding this comment

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

LGTM

@warunalakshitha warunalakshitha merged commit c470b98 into ballerina-platform:main Mar 23, 2026
3 checks passed
@snelusha snelusha deleted the chore/fix-action-runners branch April 1, 2026 14:34
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.

Update GitHub Actions to use Node 24

2 participants