Git tag releases

[greenwellness]

Hi there,

Would it by any chance be possible to adhere to semantic versioning convention of module releases (e.g. 0.1.0 or v0.1.0 not VER-0.1.0). You are already using tags but composer doesn't pick up on them. I assume you reported this package at packagist? Or is the composer.json solely for dependency management and less about publishing? In that case, the VER- named tags may be intermediate ones not intended for actual release (but I highly doubt that since they are numbered and sequential).

Using dev-master now and this is far from ideal because we won't pick up on any bumps on your side and composer is bound to break on update.

[Techworker]

Same issue for me here