Closed BehindTheMath closed 6 years ago
@BehindTheMath We could just make the next milestone 1.0.0, as things like making Pjax an event emitter will be breaking API changes that should trigger a major version bump, according to SemVer. (Technically, as we've added a few new features that are backwards-compatible in this release, SemVer would dictate that this release be 0.3.0.)
If I'm not mistaken, for versions lower than v1.0.0, everything jumps 1 position to the right. So patches and backwards-compatible changes bump the patch number, and breaking changes bump the minor version number, since you don't want to go above 1.0.0 yet.
Ah yes, you are right -- major version 0 is considered to be development, so the public API rules that dictate bumping don't apply yet. Let's go with your plan then!
v0.2.6 has been pushed to npm.
These are all bug fixes, so I think 0.2.6 is best for now.
I would like to make the next version 0.3.0 so we can implement some of the breaking changes we discussed. If that goes smoothly, I think we can release 1.0.0.