kube: resolver 1 fallback does not work in edition 2021
Trying to figure out why this is. Have tried setting resolver = "1" to get the old behaviour, but getting the k8s-openapi compile time failure when publishing.
might open a bug upstream 🤔
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 28 (25 by maintainers)
Thank you for your help with is. It was ultimately a version mismatch stemming from my belief that version = “0” would choose the correct “major” version of k8s-openapi. That doesn’t seem to be the case, so I’ll make sure to specify 0.X.
I just found this page: https://docs.rs/releases/queue
kube-coreis 134th.Everyone is releasing today
Yeah, let’s can open a new issue on MSRV.
Yeah, it’s been taking longer and longer between docs.rs publishes, so was hoping this is just a long queue on their end. I was going to tweet, but have to wait for docs. I don’t think it’s related to the bootstrapping problem though because that should only affect
kube-runtime(it was the only crate i had to hack during the publish cycle).@clux Tokio doesn’t really have external dependencies that aren’t also maintained by Tokio maintainers…
For a higher level project like this, it’s going to be dependent on the upstream compatibility policies. Six months, though, does seem like a good target to me, if possible.
Sure. I’ll prepare a PR for backing out the backout.
Yes, looks like we just need to set
enable-featuresinrelease.toml: https://github.com/crate-ci/cargo-release/blob/master/docs/reference.md