The problem with semver is the actual lack of tooling built around semver. Humans aren't robots, a bug fix might actually be a breaking change, without the author noticing it. What to do in that case. Yet semver is…
> tl;dr: There are next to no "backwards compatible API changes" in go. You should explicitely name your compatibility-guarantees. It's not a problem in languages that come with a package manager, or at least promote a…
The problem with semver is the actual lack of tooling built around semver. Humans aren't robots, a bug fix might actually be a breaking change, without the author noticing it. What to do in that case. Yet semver is…
> tl;dr: There are next to no "backwards compatible API changes" in go. You should explicitely name your compatibility-guarantees. It's not a problem in languages that come with a package manager, or at least promote a…