-
Notifications
You must be signed in to change notification settings - Fork 9.7k
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
go get is failing #12412
Comments
"We need to tag the repository properly as 3.5.0-pre to make it work. Will try to do this this week. For now please depend on the 3.4 branch where client is part of the server. If you want to depend on release 3.4.13, please use: Don't worry about:
You will find in the go.mod file." |
Alternatively, you can replace those modules:
|
FYI: The script to make a proper release of e.g. |
Awesome! I'm really looking forward to it. It'll help the ecosystem a lot as a bunch of basic packages (eg. Viper) depend on etcd and pulls in a plethora of unnecessary dependencies. |
My favorite dependency cycle: |
Yeah, that's a disaster. Go kit should really be split up into modules as well. |
I'm not sure if this is related, so please bear with me... I'm trying to update my client from 3.3.x to 3.4.x and it is also failing to # go get go.etcd.io/etcd/client/v3
go: go.etcd.io/etcd/client/v3 upgrade => v3.0.0-20201109164711-01844fd28560
go get: go.etcd.io/etcd/client/v3@v3.0.0-20201109164711-01844fd28560 requires
go.etcd.io/etcd/api/v3@v3.0.0-00010101000000-000000000000: invalid version: unknown revision 000000000000 Maybe the client should not really move from Also, https://etcd.io/docs/v3.4.0/integrations/ mentions the BTW, this seems related to #12464, maybe my question belongs there? |
I have the same problem 😭 |
|
FYI: The release of 3.5.0-alpha.0 is tracked by: #12498 |
If you want to test is earlier you can play with my fork of the release:
|
This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 21 days if no further activity occurs. Thank you for your contributions. |
The text was updated successfully, but these errors were encountered: