-
Notifications
You must be signed in to change notification settings - Fork 27
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
API breakage and module version: Element.remove #24
Comments
Agreed. Looks like we originally missed that when releasing 0.1.6. |
Sadly version 0.1.6 has already been released on npm so there is not much I can do now. I could release a new version and call it 0.2.0 (or just switch to 2.0.0), but this still won't fix a "problem" with 0.1.6 (removing / deleting a version from 0.1.6 would just be a bad idea). |
Sorry for the late reply :) My suggestion is going forward for the next release you increment the major version (like you mentioned, 2.0.0 or equivalent) |
This commit for 0.1.6: 10b3b8c
Not sure if you care about semver, but ideally since this is an incompatible API change from 0.1.5, the major version should have been bumped (or at least doc'ed)
The text was updated successfully, but these errors were encountered: