-
-
Notifications
You must be signed in to change notification settings - Fork 28
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
Node16 is deprecated, need to update #77
Comments
@corneliusroemer Thanks fot the PR. Why the new major tho? (Purely out of interest since I've seen that pattern in recent weeks.) |
P.S. Will hold off releasing until @corneliusroemer responds because I feel there is something I'm missing. |
That's a good question! I suppose users like to be able to opt in to changes in node version but I don't know why. I'm not an actions author myself. I suppose if nothing but the node version changes there's no need to bump major version. This also means no one needs to update their workflows. |
As an action author this is the first time I've ran into this as well. Also this is the first time we've seen a major nodejs version bump wave going across the platform.
At this point I've purely using this action from self hosted runners myself. And with those you often have to install nodejs and provide the version you want. So I get why we see purely the nodejs version bump as the reason to do a major new version. On GitHub's hosted runners this isn't an issue tho. So I'll go ahead and tag a new major version tomorrow. |
Just released v4: https://github.com/WyriHaximus/github-action-helm3/releases/tag/v4.0.0 |
I got the following warning:
Can you update node to 20 and make a new major release? That'd be great!
The text was updated successfully, but these errors were encountered: