tagging releases? - Githubissues

blacklightcms / recurly

A Recurly API client written in golang. Actively maintained and unit tested. No external dependencies.

MIT License

41 stars 44 forks source link

tagging releases? #126

Closed bhb603 closed 5 years ago

bhb603 commented 5 years ago

Hi there,

We recently upgraded to v1.0.0 (thanks for the migration guide btw!).

Just wondering if you're planning to continue tagging stable releases with semver? E.g. I see this PR merged, which upgrades to recurly API v2.21, but there is no accompanying tag/release in this repo.

Will there be, for example a v1.1.0? Or should we assume everything in master is "stable", and I can reference the commit hash rather than a version in Gopkg.toml (we also use dep)?

cristiangraz commented 5 years ago

Hi @bhb603, assuming master is stable is a reasonable assumption for this library. I will continue tagging releases however, I just hadn't gotten around to tagging those two. I'll prepare a release today or tomorrow with those though!