-
-
Notifications
You must be signed in to change notification settings - Fork 36
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
Cannot setup job on self hosted runner #31
Comments
I am trying to verify #14, I am behind a proxy |
Well, the node version was bumped as part of #25. I think there is no requirement to use node 20 (except for that GitHub recommends it). I just pushed a branch |
Can you run your action (master branch) on a self hosted runner to see what you have? |
Yeah, I can test this later today! |
For some reasons, it is working with branch
npm install node-fetch
import fetch from "node-fetch";
import { Headers } from "node-fetch"; The problem with this line (action.yml) dynamic-badges-action/action.yml Line 82 in e9a478b
is that you force your action to run with node20 only. Current self-hosted runners use node16. So when my runner set up the job, it fails because your action force to use node20. I cannot install node20 using the setup-node action because it fails before.
|
@Schneegans I think, if you want to make your action compatible with enterprise and/or self-hosted runners, you must downgrade to node16 because this is the latest supported node version for github runners. Looks like most of the actions uses node16. Maybe for self-hosted runner compatibility!?
|
Regarding this post, Github is moving from node16 to node20 and And self-hosted runners are at version 2.311.0 but not for companies. What happenedThe current version of my Github Enterprise is 3.10.2. |
Hello,
I am having an issue using the action on a self-hosted runner. The job has not even started it fails at the
Set up job
step:I have node18 installed.
@Schneegans
Did you try to run the action on a self-hosted runner?
If yes, what node version?
The text was updated successfully, but these errors were encountered: