go.mod: change imports to github.com/distribution/distribution/v3

Go 1.13 and up enforce import paths to be versioned if a project
contains a go.mod and has released v2 or up.

The current v2.x branches (and releases) do not yet have a go.mod,
and therefore are still allowed to be imported with a non-versioned
import path (go modules add a `+incompatible` annotation in that case).

However, now that this project has a `go.mod` file, incompatible
import paths will not be accepted by go modules, and attempting
to use code from this repository will fail.

This patch uses `v3` for the import-paths (not `v2`), because changing
import paths itself is a breaking change, which means that  the
next release should increment the "major" version to comply with
SemVer (as go modules dictate).

Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
This commit is contained in:
Sebastiaan van Stijn 2020-08-24 13:18:39 +02:00
parent 6200038bc7
commit 1d33874951
No known key found for this signature in database
GPG key ID: 76698F39D527CE8C
173 changed files with 527 additions and 527 deletions

View file

@ -5,7 +5,7 @@ import (
"runtime"
"time"
"github.com/docker/distribution/uuid"
"github.com/distribution/distribution/v3/uuid"
)
// WithTrace allocates a traced timing span in a new context. This allows a
@ -33,7 +33,7 @@ import (
// If the function ran for roughly 1s, such a usage would emit a log message
// as follows:
//
// INFO[0001] this will be the log message trace.duration=1.004575763s trace.func=github.com/docker/distribution/context.traceOperation trace.id=<id> ...
// INFO[0001] this will be the log message trace.duration=1.004575763s trace.func=github.com/distribution/distribution/context.traceOperation trace.id=<id> ...
//
// Notice that the function name is automatically resolved, along with the
// package and a trace id is emitted that can be linked with parent ids.