Yicong-Huang opened a new issue, #4647:
URL: https://github.com/apache/texera/issues/4647

   ### Task Summary
   
   GitHub Actions runners are deprecating Node.js 20. Recent CI runs surface 
this warning (e.g., on `actions/github-script@v7`):
   
   > Node.js 20 actions are deprecated. The following actions are running on 
Node.js 20 and may not work as expected: 
`actions/github-script@60a0d83039c74a4aee543508d2ffcb1c3799cdea`. Actions will 
be forced to run with Node.js 24 by default starting June 2nd, 2026. Node.js 20 
will be removed from the runner on September 16th, 2026.
   
   References: [GitHub 
changelog](https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/).
   
   Audit and bump every Node.js-based action used under `.github/workflows/` to 
a version that ships Node 24. Known offenders today:
   
   - `actions/github-script@v7` — used in `auto-assign.yml`, 
`issue-triage.yml`. Bump to `@v8` (already in use in `required-checks.yml` and 
`direct-backport-push.yml`).
   - `actions/checkout@v4` — used in `automatic-email-notif-on-ddl-change.yml`, 
`check-header.yml`, `create-release-candidate.yml`. Bump to `@v5`.
   
   Likely also need review (still on Node 20 as of writing): 
`actions/cache@v4`, `actions/upload-artifact@v4`, 
`actions/download-artifact@v4`, `actions/labeler@v6`. Check upstream release 
notes for Node 24 support and pin to the first version that supports it.
   
   Third-party actions (SHA-pinned today) similarly need a Node 24 audit: 
`sbt/setup-sbt`, `coursier/cache-action`, `docker/setup-buildx-action`, 
`docker/login-action`, `docker/build-push-action`, `docker/setup-qemu-action`, 
`apache/skywalking-eyes`.
   
   ### Priority
   
   P3 – Low (blocking deadlines: 2026-06-02 forced Node 24, 2026-09-16 Node 20 
removed)
   
   ### Task Type
   
   - [x] DevOps / Deployment


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to