Update action to node v16 #285
Assignees
Labels
Milestone
Comments
jontze
added
enhancement
jontze
added a commit
that referenced
this issue
Nov 30, 2022
This was required as github deprecates all node v12 actions: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/ Further node12 is no longer maintained: https://github.com/nodejs/release#release-schedule The action will still work as before. But dropping support for node v12 is considered as a BREAKING CHANGE. Close #285
jontze
added a commit
that referenced
this issue
Dec 7, 2022
This was required as github deprecates all node v12 actions: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/ Further node12 is no longer maintained: https://github.com/nodejs/release#release-schedule The action will still work as before. But dropping support for node v12 is considered as a BREAKING CHANGE. Close #285
jontze
added a commit
that referenced
this issue
Dec 7, 2022
This was required as github deprecates all node v12 actions: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/ Further node12 is no longer maintained: https://github.com/nodejs/release#release-schedule The action will still work as before. But dropping support for node v12 is considered as a BREAKING CHANGE. Close #285 BREAKING CHANGE
jontze
added a commit
that referenced
this issue
Dec 7, 2022
This was required as github deprecates all node v12 actions: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/ Further node12 is no longer maintained: https://github.com/nodejs/release#release-schedule The action will still work as before. But dropping support for node v12 is considered as a BREAKING CHANGE. Close #285
jontze
added a commit
that referenced
this issue
Dec 7, 2022
This was required as github deprecates all node v12 actions: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/ Further node12 is no longer maintained: https://github.com/nodejs/release#release-schedule The action will still work as before. But dropping support for node v12 is considered as a BREAKING CHANGE. Close #285
jontze
added a commit
that referenced
this issue
Dec 7, 2022
This was required as github deprecates all node v12 actions: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/ Further node12 is no longer maintained: https://github.com/nodejs/release#release-schedule Close #285 BREAKING CHANGE: Dropping support for node v12.
github-actions bot
pushed a commit
that referenced
this issue
Dec 7, 2022
# [2.0.0](v1.1.1...v2.0.0) (2022-12-07) * feat!: Update action to node v16 ([cde4bfc](cde4bfc)), closes [#285](#285) ### BREAKING CHANGES * Dropping support for node v12.
|
🎉 This issue has been resolved in version 2.0.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As node 12 is out of support since April 2022 github has deprecated actions that run on v12. Therefore we have to bump the node version of the action to v16. This is a breaking change and will be released with v2.
https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/
The text was updated successfully, but these errors were encountered: