We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
go version
$ go version go version 1.16.4 linux/amd64
Yes
go env
$ go env GO111MODULE="auto" GOARCH="amd64" GOBIN="" GOCACHE="/home/vagrant/.cache/go-build" GOENV="/home/vagrant/.config/go/env" GOEXE="" GOFLAGS="" GOHOSTARCH="amd64" GOHOSTOS="linux" GOINSECURE="" GOMODCACHE="/home/vagrant/go/pkg/mod" GONOPROXY="" GONOSUMDB="" GOOS="linux" GOPATH="/home/vagrant/go" GOPRIVATE="" GOPROXY="https://proxy.golang.org,direct" GOROOT="/opt/golang1.16/lib/golang" GOSUMDB="sum.golang.org" GOTMPDIR="" GOTOOLDIR="/opt/golang1.16/lib/golang/pkg/tool/linux_amd64" GOVCS="" GOVERSION="1.16.4" GCCGO="gccgo" AR="ar" CC="/opt/gcc8/bin/gcc8" CXX="g++" CGO_ENABLED="1" GOMOD="" CGO_CFLAGS="-g -O2" CGO_CPPFLAGS="" CGO_CXXFLAGS="-g -O2" CGO_FFLAGS="-g -O2" CGO_LDFLAGS="-g -O2" PKG_CONFIG="pkg-config" GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build3330331572=/tmp/go-build -gno-record-gcc-switches"
Using the golang.org/x/crypto pkg and noticed that it doesn't use the standard Go Modules versioning. Ie, the repository does not have any git tags.
golang.org/x/crypto
Proper git tags (vX.X.X) on golang.org/x/crypto so one can easily identify which version of the pkg they are using.
golang.org/x/crypto was updated to have a go.mod file but never went the full path of adding git tags with proper version semantics.
go.mod
The text was updated successfully, but these errors were encountered:
Duplicate of #21324
Sorry, something went wrong.
No branches or pull requests
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
Using the
golang.org/x/crypto
pkg and noticed that it doesn't use the standard Go Modules versioning. Ie, the repository does not have any git tags.What did you expect to see?
Proper git tags (vX.X.X) on
golang.org/x/crypto
so one can easily identify which version of the pkg they are using.What did you see instead?
golang.org/x/crypto
was updated to have ago.mod
file but never went the full path of adding git tags with proper version semantics.The text was updated successfully, but these errors were encountered: