Don't think of it as /version/ pinning. Think of it as Interface / API pinning. A //public library// should have a well thought out interface that works at le

Don't think of it as /version/ pinning. Think of it as Interface / API pinning. A //public library// should have a well thought out interface that works at least for one project and preferably for several different projects. If the interface needs to change I agree with the recommended semantics of planning what that change should look like and creating a new named interface (API) for that specification. Since go expects everything to build against the 'latest' version of an interface, it should be obvious what's wrong if a stale cached version is in use. Thus /expanding/ an interface / API is permissible. They should be thought of as /write only/.