Skip to content
New issue

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

Update Published Go Packages #3991

Closed
dtzar opened this issue Sep 10, 2020 · 4 comments
Closed

Update Published Go Packages #3991

dtzar opened this issue Sep 10, 2020 · 4 comments
Labels
solution/workaround There's a workaround, might not be great, but exists type/feature Feature request
Milestone

Comments

@dtzar
Copy link

dtzar commented Sep 10, 2020

Summary

Update published Golang packages on pkg.go.dev

Use Cases

When would you use this?

go get naturally tries to pull from the published pkg.go.dev source and this source has not been updated since February 2020. This makes pinning to a newer version more challenging. Ideally there would be a corresponding published packaged at least for every release on the repo.

Minor nit: the website also believes 0.4.7 is the "latest" version.

@alexec
Copy link
Contributor

alexec commented Sep 10, 2020

The reason that this happens is that we migrated to Gomodules, and Gomodules broken this.

See #3192

@alexec
Copy link
Contributor

alexec commented Sep 10, 2020

Work-around: #2602 (comment)

@alexec alexec added wontfix solution/workaround There's a workaround, might not be great, but exists labels Sep 10, 2020
@stale stale bot removed the wontfix label Sep 10, 2020
@alexec alexec added this to the v3.0 milestone Dec 20, 2020
@alexec
Copy link
Contributor

alexec commented Dec 20, 2020

@dtzar do you know how to fix this please?

@alexec
Copy link
Contributor

alexec commented Apr 1, 2021

Should be fixed now? https://pkg.go.dev/github.com/argoproj/argo-workflows/v3

@alexec alexec closed this as completed Apr 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
solution/workaround There's a workaround, might not be great, but exists type/feature Feature request
Projects
None yet
Development

No branches or pull requests

2 participants