-
-
Notifications
You must be signed in to change notification settings - Fork 320
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
upgrade to tower 0.5.0 #1569
Comments
...yeah, this one must wait one release. The tower 0.5.0 release is the first release since march 2022, there are no migration notes, and the PRs referenced are from this whole time period (2.5 years). I expect this one will be fun when it's possible. Right now it looks impossible without ecosystem propagation. The rustls ecosystem pulls in 0.4.13 and there are type mismatches in errors: $ cargo tree -i [email protected]
tower v0.5.0
└── kube-client v0.93.1 (/home/clux/kube/kube/kube-client)
└── kube v0.93.1 (/home/clux/kube/kube/kube)
$ cargo tree -i [email protected]
tower v0.4.13
└── hyper-util v0.1.7
├── hyper-rustls v0.27.3
│ └── kube-client v0.93.1 (/home/clux/kube/kube/kube-client)
│ └── kube v0.93.1 (/home/clux/kube/kube/kube)
├── hyper-timeout v0.5.1
│ └── kube-client v0.93.1 (/home/clux/kube/kube/kube-client) (*)
└── kube-client v0.93.1 (/home/clux/kube/kube/kube-client) (*) Marking as blocked for now. |
fixes kube-rs#1569 Signed-off-by: Mark Ingram <[email protected]>
fixes kube-rs#1569 Signed-off-by: Mark Ingram <[email protected]>
fixes kube-rs#1569 Signed-off-by: Mark Ingram <[email protected]>
fixes kube-rs#1569 Signed-off-by: Mark Ingram <[email protected]>
fixes kube-rs#1569 Signed-off-by: Mark Ingram <[email protected]>
violently failed ci from dependabot in #1561
not sure if this is going to be hard or not. will have a look on the weekend to see if this worth doing before next release.
tower 0.5.0 changes
The text was updated successfully, but these errors were encountered: