Skip to content

Conversation

@salmanmkc
Copy link
Contributor

@salmanmkc salmanmkc commented Dec 13, 2025

Summary

Updates all actions/* GitHub Actions to their latest versions to ensure compatibility with Node.js 24 and prepare for the deprecation of Node.js 20 on GitHub Actions runners.

Changelog:

[Internal] [Changed] - Updated GitHub Actions to latest versions with Node.js 24 support

Version Updates

Action Previous Current Release Notes
actions/checkout v4 v6 v6.0.0
actions/github-script v6 v8 v8.0.0
actions/setup-node v4 v6 v6.0.0
actions/setup-java v2/v4 v5 v5.0.0
actions/upload-artifact v4/v4.3.4 v6 v6.0.0
actions/download-artifact v4/v4.1.3 v7 v7.0.0
actions/cache v4 v5 v5.0.0
actions/stale v9 v10 v10.0.0

Why

GitHub is deprecating Node.js 20 on Actions runners. The new versions of these actions now run on Node.js 24 by default (runs.using: node24).

Requirements

  • Minimum Actions Runner version: v2.327.1
  • Self-hosted runners should be updated before merging

Test Plan

  • PR-triggered workflows (test-all.yml, danger-pr.yml) will validate core CI
  • Other workflows will be validated when their respective triggers occur (schedules, releases, issue events)

…upport

## Summary

Update all `actions/*` GitHub Actions to their latest versions to ensure
compatibility with Node.js 24 and prepare for the deprecation of Node.js 20
on GitHub Actions runners.

See: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/

## Version Updates

| Action | Previous | Current |
|--------|----------|---------|
| actions/checkout | v4 | v6 |
| actions/github-script | v6 | v8 |
| actions/setup-node | v4 | v6 |
| actions/setup-java | v2/v4 | v5 |
| actions/upload-artifact | v4/v4.3.4 | v6 |
| actions/download-artifact | v4/v4.1.3 | v7 |
| actions/cache/restore | v4 | v5 |
| actions/cache/save | v4 | v5 |
| actions/stale | v9 | v10 |

## Key Changes

- All actions now run on Node.js 24 by default
- Minimum Actions Runner version required: v2.327.1
- Updated 32 workflow and composite action files

## Test Plan

- PR-triggered workflows (test-all.yml, danger-pr.yml) will validate core CI
- Other workflows will be validated when their respective triggers occur (schedules, releases, issue events)
@meta-cla meta-cla bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Dec 13, 2025
@facebook-github-bot facebook-github-bot added the Shared with Meta Applied via automation to indicate that an Issue or Pull Request has been shared with the team. label Dec 13, 2025
@cipolleschi
Copy link
Contributor

@salmanmkc Amazing job, thanks for taking the time and updating our CI pipeline.
I kickstarted all the CI jobs, if everything is green, we can import and land!

@meta-codesync
Copy link

meta-codesync bot commented Dec 15, 2025

@cipolleschi has imported this pull request. If you are a Meta employee, you can view this in D89178299.

@meta-codesync meta-codesync bot closed this in b9ac408 Dec 15, 2025
@meta-codesync
Copy link

meta-codesync bot commented Dec 15, 2025

@cipolleschi merged this pull request in b9ac408.

@facebook-github-bot facebook-github-bot added the Merged This PR has been merged. label Dec 15, 2025
@react-native-bot
Copy link
Collaborator

This pull request was successfully merged by @salmanmkc in b9ac408

When will my fix make it into a release? | How to file a pick request?

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

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. Merged This PR has been merged. Shared with Meta Applied via automation to indicate that an Issue or Pull Request has been shared with the team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants