Replies: 1 comment
-
|
Sorry, it looks like I was confused about the reason for failure. The "Node.js" thing was just an annoying warning. Why is that happening? |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
🏷️ Discussion Type
Question
💬 Feature/Topic Area
Actions Checkout
Discussion Details
I created my first action containing multiple jobs. The first being a "setup" job that others depend upon. That "setup" job is failing with a complaint about Node.js version when I am not specifying anything that has to do with JS. The relevant section of the action is:
The action looks like it is running as expected, but the "setup" job fails with the following message:
Node.js 20 is deprecated. The following actions target Node.js 20 but are being forced to run on Node.js 24: actions/setup-java@v4. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/Although the provided URL has an explanation of the "20 vs. 24" issue, I do not see the actual relevance to this action since nothing is directing it to do anything that is not default.
The relevant steps were originally copied from the "Java using Ant" template.
I changed the "checkout@v4" to request v6 after researching this same error on the first run.
My "on" statement uses a "workflow_dispatch" and that all seems to be working fine.
You can see some of the other things that I tried without success in the comments.
Beta Was this translation helpful? Give feedback.
All reactions