Neither API nor Behavior of your module has changed, so it's definitionally
a patch release. Go modules have an explicit design goal to enable using
multiple major versions of a module in the same binary. i.e. your situation
is basically what's described here as a motivation for semantic import
ver
Hi,
playing around with the go modules, I wondered:
Let's say, my library gets a compatible update. The only thing that changes
is, I have updated a dependency to an incompatible major version and
changed the internal library code accordingly. However the behavior and API
of my library
did not
