-
Notifications
You must be signed in to change notification settings - Fork 149
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
New release to support node20? #278
Comments
GitHub actions now logs a warning when running actions using Node 16. This is the line for
|
also cc @filmaj, who appears to be assigned to many of the tasks for the |
This was a breaking change, we've had to pin our version to v1.24 now as runners without node20 support will fail.
|
Description
I have node v20 on my self-hosted action runner, but the latest release (v1.24.0) of slack-github-action requires node v18.
I tried to use
slackapi/slack-github-action@main
, butdist/index.js
is missing. I ended up forkingmain
and runningnpm ci && npm run build
to make a node20 compatible version here, but it's not quite clean.I don't quite understand the branching model that this repo uses to cut releases. Could a maintainer perhaps cut a 1.25.0 release from the main branch with official node20 support? Thanks.
What type of issue is this? (place an
x
in one of the[ ]
)Requirements (place an
x
in each of the[ ]
)Bug Report
Reproducible in: 1.24.0
package version: github-runner-2.311.0
node version: 20.9.0 (nodejs_20)
OS version(s): NixOS 23.11
Steps to reproduce:
slackapi/[email protected]
Expected result:
Workflow would use node20, or there would be a tagged release that uses node20
Actual result:
Failure running workflow when it tries to find node16. Latest v1.24.0 release only works on node16, and there is no way to select a git commit from the current
main
branch for node20 support.The text was updated successfully, but these errors were encountered: