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.

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

proposal: Bump node from 12 to 16 #677

Closed
3 tasks done
peaceiris opened this issue Dec 8, 2021 · 7 comments · Fixed by #791
Closed
3 tasks done

proposal: Bump node from 12 to 16 #677

peaceiris opened this issue Dec 8, 2021 · 7 comments · Fixed by #791
Assignees

Comments

@peaceiris
Copy link
Owner

Checklist

  • I am using the latest version of this action.
  • I have read the latest README and followed the instructions.
  • I have read the latest GitHub Actions official documentation and learned the basic spec and concepts.

Describe your proposal

Bump runtime version from node12 to node16

Describe the solution you'd like

  • update action.yml
  • update test
  • update CI

Describe alternatives you've considered

N/A

Additional context

@peaceiris peaceiris self-assigned this Dec 8, 2021
@yashash-pugalia
Copy link

node18 was released today.

@unional
Copy link

unional commented Oct 11, 2022

GitHub is emitting warnings:

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: peaceiris/actions-gh-pages

tgrall added a commit to tgrall/actions-gh-pages that referenced this issue Oct 15, 2022
@peaceiris peaceiris mentioned this issue Oct 17, 2022
3 tasks
@mo3et
Copy link

mo3et commented Oct 18, 2022

I want to know when to bump the node from 12 to 16 for the release version.

@peaceiris
Copy link
Owner Author

I am planning the next major release from node12 to node16 this weekend.

@mo3et
Copy link

mo3et commented Oct 20, 2022

I am planning the next major release from node12 to node16 this weekend.

OK! thanks.

@peaceiris
Copy link
Owner Author

@github-actions
Copy link
Contributor

This issue has been LOCKED because of it being resolved!

The issue has been fixed and is therefore considered resolved.
If you still encounter this or it has changed, open a new issue instead of responding to solved ones.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 24, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants