-
Notifications
You must be signed in to change notification settings - Fork 87
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
refactor!: migrate to esm and update dependencies #256
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If we merge will semantic release cut a release? Should we batch this with the other breaking changes?
I don't know. Let me update other deps in this one then. |
I think we need to update |
Looks like the refactor didn't trigger a release, but I imagine the next one will be breaking. |
Looks like the breaking change should trgger by the commit message footer https://semantic-release.gitbook.io/semantic-release/#how-does-it-work |
🎉 This PR is included in version 1.56.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This should have been a major version bump. |
)" This reverts commit 3e4ff74.
@fisker @keithamus This should have been in a breaking/major release. I created #259 to revert this PR. |
Fixes #254
Fixes #247
Fixes #227
Closes #255
[BREAKING]: Require Node.js 12