Request: tag a release

[AkihiroSuda]

For ease of dependency management, could you consider creating a release with git tag?

[AkihiroSuda]

Linking related discussion : compose-spec/compose-spec#104 (comment)

[alexellis]

We could really use a release here too @ndeloof for the usage in faasd

Recent breaking changes in master the Go library have broken our usage, so we're having to pin to an old commit. It's harder to understand what changes are being made without any versions being cut, so what do you think about starting to create tags?

[ndeloof]

I'd like we adopt something extra-simple to define tagged releases. compose-spec/compose-spec#171 is still way too complex imho as it still require maintainers to agree on good time for a release...
I'd suggest we adopt a "Jenkins-style" weekly release cycle, i.e. have a cron job to tag and release v1.xxx wdyt?

it's harder to understand what changes are being made without any versions being cut

Maybe this is just me, but I don't think tags would make this easier. git bisect to rule them all :P

[AkihiroSuda]

https://github.com/compose-spec/compose-go/releases/tag/v1.0.1 🎉
Thanks!