Tagging stable versions to ease

[firuzz]

Hi @aidansteele 👋,

First of all, thanks for keeping sphlib available here — it’s great that this code is still accessible to the community after all these years.

I’m currently using this repository as a dependency in a Conan 2 package recipe. In that context, it’s standard practice to fetch sources using version tags, since tags provide a stable reference for reproducible builds.

I noticed that the repository only has the master branch and no tags or releases. Would you consider adding a tag (for example, v3.0) to the original commit 3ef160b2ed8e4a8d94325c51b4706ef8178ee424 whose message reads “Initial commit of sphlib 3.0”?

That would allow me (and probably others packaging or consuming this library) to reference the classic version cleanly, while the newer commit remains available for those who want to use or build upon it.

Thanks a lot for your time and for keeping this project alive!