Please use semver for release tags

[metalurgical]

Swift Package Manager expects SemVer versioning.

https://developer.apple.com/documentation/xcode/publishing-a-swift-package-with-xcode#Tag-your-latest-commit

Currently there are a number of breaking changes in previously released versions which is making it very difficult to find compatible versions of this library between different libraries using this one as a dependency. This is due to .exact() being used instead of from: for this library to avoid the breaking changes.

If you look at 0.10.0, there is a breaking change at 0.12.1, thereafter there is another breaking change leading up to 0.15.0.

[csjones]

Hey @metalurgical 👋

Thanks for raising your concern. In response to your message, it's important to note that using a major version of 0 in Semantic Versioning (SemVer) is valid and indicates the software is in its initial development phase. During this phase, breaking changes are expected with minor version increments (as seen in your 0.y.z versions).

My approach aligns with SemVer principles, where the API is not considered stable until reaching version 1.0.0. The link you posted references the Semantic Versioning spec which states the following:

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

Additionally, this repository's readme includes a similar notice. https://github.com/GigaBitcoin/secp256k1.swift?tab=readme-ov-file#danger

If you have any further concerns or believe there's more to address, feel free to leave a comment. 🙂