-
Notifications
You must be signed in to change notification settings - Fork 16
Description
Issue
Github actions are deprecating support for node 20. ipfs/ipfs-deploy-action@v1 seems to be using older action versions that are deprecated.
https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
This warning message is appearing in the workflow
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/cache/restore@v4, actions/github-script@v7, actions/upload-artifact@v4. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
Investigation
Checking the dependencies that the action uses, I can see a couple that may need to have their versions bumped
https://github.com/ipshipyard/ipfs-deploy-action/blob/main/action.yml
-
actions/github-script@v7
Line 318 in 6ce76b7
uses: actions/github-script@v7
Currently usesv7, which is on node 7.
Would want to bump tov8which uses node 24
https://github.com/actions/github-script?tab=readme-ov-file#breaking-changes -
actions/upload-artifact@v4
Line 170 in 6ce76b7
uses: actions/upload-artifact@v4
Currently usesv4which is on node 20
Would want to bump tov6which uses node 24 -
actions/cache/restore@v4
v4is node 20
need to bump tov5
https://github.com/actions/cache?tab=readme-ov-file#v5
I can't find a direct reference to using the cache action, I think it is being used by actions/upload-artifact@v4. Bumping that to v6 may resolve this one also.