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

fix(engines): drop support for versions of node that are out of maintenance #849

Merged
merged 2 commits into from
Jun 21, 2021

Conversation

hughrawlinson
Copy link
Member

If we merge #841 first, we should also remove these nodes from the build matrix in the github actions workflow!

BREAKING CHANGE: remove nodes 10 and 13

fix #842

…enance

BREAKING CHANGE: remove nodes 10 and 13

fix #842
@hughrawlinson
Copy link
Member Author

If we merge this to a pre-release branch, semantic release will (should? If I set it up correctly on Actions) publish betas. We could do this for all the breaking changes. I think that'd be a good way to ask people to try things out before releasing.

@hughrawlinson hughrawlinson merged commit 4f5a118 into v6 Jun 21, 2021
@hughrawlinson hughrawlinson deleted the drop-old-nodes branch June 21, 2021 07:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

Drop Node 10 and 13 in next major release
1 participant