Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Update NodeJS from 12 to 16 #15

Open
Wohlstand opened this issue Oct 25, 2022 · 3 comments · May be fixed by #17
Open

Update NodeJS from 12 to 16 #15

Wohlstand opened this issue Oct 25, 2022 · 3 comments · May be fixed by #17

Comments

@Wohlstand
Copy link

Because your module uses Node12, it reports to me next:

изображение

Node.js 12 actions are deprecated. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/. Please update the following actions to use Node.js 16: nelonoel/branch-name

https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/
@andylamp
Copy link

given that the deprecation date approaches - do you have an update on this? As pretty much this project seems kind of abandoned...

@Wohlstand
Copy link
Author

Wohlstand commented Jan 11, 2023 •
edited
Loading

As a temporary workaround, you can use the next thing:

    - uses: Wohlstand/[email protected]

It is my private fork where I fixed the NodeJS versions to use with my projects, but I hadn't to publish it widely and still keeping it as my private thing with a hope that mainstream author will wake up after a long term sleep and apply the fix officially.

@andylamp
Copy link

I really have no issue with him not having the time to fix this or even bother... just want visibility so I can either fix it myself through a fork or look elsewhere! Thanks for the suggested fix!

christianspecht added a commit to christianspecht/blog that referenced this issue May 15, 2023
@christianspecht
update to Node 16 actions
fc1ec1d 
https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/

The new branch-name action came from here:
nelonoel/branch-name#15
@christianhelle christianhelle linked a pull request Aug 8, 2023 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use Node v16 instead of v12 christianhelle/branch-name
2 participants
@andylamp @Wohlstand