You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
How can I refer to a release as a Go module dependency?
The current tag naming scheme seems to tag the 1.2.2 release as v1beta2-1.2.2-3.0.0. This format does not seem to follow the semantic versioning scheme that Go modules expect, but I could be wrong.
This may just be related to #1198, but here is what I've tried.
$ go mod init example.com/m
$ go get k8s.io/client-go
$ go get k8s.io/apiextensions-apiserver
$ go get github.com/GoogleCloudPlatform/[email protected]
go get: github.com/GoogleCloudPlatform/spark-on-k8s-operator@none updating to
github.com/GoogleCloudPlatform/[email protected] requires
k8s.io/[email protected]: reading k8s.io/apiextensions-apiserver/go.mod at revision v0.0.0: unknown revision v0.0.0
Alternatively, I tried to use the k8s.io version specified in the v1beta2-1.2.2-3.0.0 release.
$ go mod init example.com/m
$ go get k8s.io/[email protected]
$ go get github.com/GoogleCloudPlatform/[email protected]
go get: github.com/GoogleCloudPlatform/spark-on-k8s-operator@none updating to
github.com/GoogleCloudPlatform/[email protected] requires
k8s.io/[email protected]: reading k8s.io/apiextensions-apiserver/go.mod at revision v0.0.0: unknown revision v0.0.0
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
How can I refer to a release as a Go module dependency?
The current tag naming scheme seems to tag the 1.2.2 release as
v1beta2-1.2.2-3.0.0
. This format does not seem to follow the semantic versioning scheme that Go modules expect, but I could be wrong.This may just be related to #1198, but here is what I've tried.
Alternatively, I tried to use the k8s.io version specified in the v1beta2-1.2.2-3.0.0 release.
The text was updated successfully, but these errors were encountered: