int128 / int128/deploy-lambda-action
Upgrade to node 24
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5
- Forks
- 5
- Avg merge
- 21m
- Merged PRs (30d)
- 43
Description
Hi when is an upgrade to node 24 coming for this or is planned ?
In github actions we are getting a warning
Warning: Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: int128/deploy-lambda-action@a705d29da4808a75e25134d2652b6d565af8c76b. 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/
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by checking the GitHub Actions configuration that invokes int128/deploy-lambda-action@a705d29da4808a75e25134d2652b6d565af8c76b and identify where its Node runtime is defined. Confirm the action runs on Node 24 and that the deprecation warning is gone.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, github-actions, nodejs, typescript
- Domain
- ci-cd, cloud
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100