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 versioning: https://research.swtch.com/vgo-import
On Wed, Aug 15, 2018 at 11:40 AM 'meta keule' via golang-nuts < golang-nuts@googlegroups.com> wrote: > > 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 change. > > Should I then tag the new version as a patch or as a new major version? > > What do you think? > > - benny > > > -- > You received this message because you are subscribed to the Google Groups > "golang-nuts" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to golang-nuts+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
