-
Notifications
You must be signed in to change notification settings - Fork 102
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
Drop Node 10 and 13 in next major release #842
Labels
Comments
hughrawlinson
added a commit
that referenced
this issue
May 30, 2021
…enance BREAKING CHANGE: remove nodes 10 and 13 fix #842
hughrawlinson
added a commit
that referenced
this issue
May 30, 2021
…enance BREAKING CHANGE: remove nodes 10 and 13 fix #842
hughrawlinson
added a commit
that referenced
this issue
May 30, 2021
…enance BREAKING CHANGE: remove nodes 10 and 13 fix #842
hughrawlinson
added a commit
that referenced
this issue
Jun 21, 2021
…enance BREAKING CHANGE: remove nodes 10 and 13 fix #842
hughrawlinson
added a commit
that referenced
this issue
Jul 17, 2021
…enance BREAKING CHANGE: remove nodes 10 and 13 fix #842
hughrawlinson
added a commit
that referenced
this issue
Jul 17, 2021
…enance BREAKING CHANGE: remove nodes 10 and 13 fix #842
🎉 This issue has been resolved in version 6.0.0-beta.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
hughrawlinson
added a commit
that referenced
this issue
Oct 31, 2021
…enance BREAKING CHANGE: remove nodes 10 and 13 fix #842
hughrawlinson
added a commit
that referenced
this issue
Oct 31, 2021
…enance BREAKING CHANGE: remove nodes 10 and 13 fix #842
hughrawlinson
added a commit
that referenced
this issue
Nov 13, 2021
…enance BREAKING CHANGE: remove nodes 10 and 13 fix #842
hughrawlinson
added a commit
that referenced
this issue
May 11, 2022
…enance BREAKING CHANGE: remove nodes 10 and 13 fix #842
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I was tempted to do it now since both have dropped out of maintenance, but I've seen other maintainers treat it as a breaking change despite that.
The text was updated successfully, but these errors were encountered: