distribution/version/version.go

package version

// Package is the overall, canonical project import path under which the
// package was built.
var Package = "github.com/distribution/distribution/v3"

// Version indicates which version of the binary is running. This is set to
// the latest release tag by hand, always suffixed by "+unknown". During
// build, it will be replaced by the actual version. The value here will be
// used if the registry is run after a go get based install.
var Version = "v3.0.0-alpha.1"

// Revision is filled with the VCS (e.g. git) revision being used to build
// the program at linking time.
var Revision = ""
Report version in registry binary We've added support to the registry command to report the current version of the distribution package. The version package is generated with a shell script that gets the latest tag and add "+unknown". This allows builds from "go get" and "go install" to have a rough version number. Generated periodically, it will provide a decent indication of what code built the binary. For more accurate versioning, one can build with the "binaries" make target. Linker flags are used to replace the version string with the actual current tag at build time. Signed-off-by: Stephen J Day <stephen.day@docker.com> 2015-01-29 23:32:49 +00:00			`package version`

			`// Package is the overall, canonical project import path under which the`
			`// package was built.`
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> 2020-08-24 11:18:39 +00:00			`var Package = "github.com/distribution/distribution/v3"`
Report version in registry binary We've added support to the registry command to report the current version of the distribution package. The version package is generated with a shell script that gets the latest tag and add "+unknown". This allows builds from "go get" and "go install" to have a rough version number. Generated periodically, it will provide a decent indication of what code built the binary. For more accurate versioning, one can build with the "binaries" make target. Linker flags are used to replace the version string with the actual current tag at build time. Signed-off-by: Stephen J Day <stephen.day@docker.com> 2015-01-29 23:32:49 +00:00
			`// Version indicates which version of the binary is running. This is set to`
			`// the latest release tag by hand, always suffixed by "+unknown". During`
			`// build, it will be replaced by the actual version. The value here will be`
			`// used if the registry is run after a go get based install.`
release: prep for the v3 alpha-1 release Signed-off-by: Milos Gajdos <milosthegajdos@gmail.com> 2023-12-19 12:01:20 +00:00			`var Version = "v3.0.0-alpha.1"`
Update build to use travis Update Makefile targets Signed-off-by: Derek McGowan <derek@mcgstyle.net> 2018-08-01 22:37:21 +00:00
			`// Revision is filled with the VCS (e.g. git) revision being used to build`
			`// the program at linking time.`
			`var Revision = ""`