Request for tagged releases in Git to enable downstream version pinning

[lnagel]

Hi,

We maintain pycdoc, a Python binding for libcdoc that we use in our projects. We include libcdoc as a Git submodule and build it as part of our wheel packaging process. Since libcdoc is statically linked into the extension module, we bundle the full libcdoc source in our sdist and provide relinking instructions to stay compliant with LGPL-2.1 Section 6.

We'd like to sync our releases to stable libcdoc versions, but currently there are no Git tags or GitHub releases in this repository. The only version signal we can find is the project(libcdoc VERSION X.Y.Z) line in CMakeLists.txt. This makes it difficult to reliably pin to a known-good release — we have to manually track which commit corresponds to which version.

Would you consider tagging releases in Git when you bump the version? Even lightweight tags (e.g. v0.1.8) would be very helpful for downstream consumers.

For reference, we traced the version history from CMakeLists.txt changes. Could you confirm whether this mapping looks correct?

Version	Commit	PR / Message
0.1.0	6adc284	Initial
0.1.1	f552b1c	Handle command line arguments
0.1.2	6a93b4e	Handling of decrypt parameters
0.1.3	6c02d01	Label indexing on decrypt
0.1.4	174c635	Label auto generation
0.1.5	518e5d9	Logger support
0.1.6	2e41d68	Keyshare encryption (#47)
0.1.7	a681507	Fix error handling in java wrapper (#57)
0.1.8	5410095	Fixed NetworkBackend path building (#58)

Thank you for maintaining libcdoc — it's been great to build on top of!

[metsma]

Just a warning: we still don’t provide stable releases.
The library is under heavy development, and there may be API/ABI-breaking changes.
We’re waiting for the final versions of the 1.7 and 2.0 standards.
I’ll look into the tagging.
Also, if you can provide feedback on the API, documentation, or bindings, that would be really helpful.