Ship a Gopkg.toml

Question

Ship a Gopkg.toml

lavalamp opened this issue 7 years ago · 6 comments

...to help dep users get the correct version of dependencies (e.g., k8s.io/apimachinery).

Answer 1 · 2017-09-07T18:14:28.000Z

To avoid duplicated work, I have prototype code for the publishing bot to do this when a release tag from the kube repo is converted into one of the published repo. Obviously, the Gopkg.toml should not reference sha1 revisions, but tags, for client-go preferably the semver tag.

Answer 2 · 2017-09-07T18:34:14.000Z

Yeah, maybe I filed this in the wrong place.

…

On Thu, Sep 7, 2017 at 11:15 AM, Dr. Stefan Schimanski < ***@***.***> wrote: To avoid duplicated work, I have prototype code for the publishing bot to do this when a release tag from the kube repo is converted into one of the published repo. Obviously, the Gopkg.toml should not reference sha1 revisions, but tags, for client-go preferably the semver tag. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#23 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAnglkn4QLhq8SWJWxS3QzQDgOCHb3Lpks5sgDKFgaJpZM4PQJ-y> .

Answer 3 · 2018-01-04T18:52:40.000Z

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or @fejta.
/lifecycle stale

Answer 4 · 2018-01-04T19:20:12.000Z

/assign
/lifecycle frozen

Answer 5 · 2018-03-04T05:39:50.000Z

/remove-lifecycle stale

Answer 6 · 2019-07-04T12:20:50.000Z

We have go.mod now, so closing. :)