Follow semver please?

[mrchief]

Describe the bug
In the latest release, marked went up from v0.3.18 to v.0.4.0. A minor bump indicates backward compatible changes and most importantly, no breaking changes. Yet the release notes mention several of them:

This is counterproductive. A seemingly harmless update potentially can break exiting usages.

Can we please adhere to semver guidelines?

[UziTech]

Major version zero (0.y.z) is for initial development. Anything may change at any time. The public API should not be considered stable.

https://semver.org/#spec-item-4

[UziTech]

In pre-1.0 releases the minor version is commonly used for breaking changes which is why npm has caret ranges (i.e ^0.3.0 will match >= 0.3.0 and < 0.4.0)

[mrchief]

Oh, didn't see that coming. Is there a planned v1 release anytime soon?

[mrchief]

Kickass homepage by the way! 👍

[UziTech]

We are working toward v1.0 but I think we have a long way to go. We have been trying to resurrect marked from being unmaintained for a while.

Any PRs would be greatly appreciated 😃 👍