chore(deps): bump kube 3.1 → 4.0 and k8s-openapi 0.27 → 0.28#89
Merged
Conversation
kube 3.1 pins k8s-openapi ^0.27, so moving to k8s-openapi 0.28 requires kube 4.0 (which requires ^0.28). Purely a dependency bump — no source changes; cargo check --all-targets, clippy, and the unit suite all pass unchanged. kube_quantity 0.9's loose k8s-openapi (^0) unifies onto 0.28. Also fully-specs the remaining loose dependency versions (mimalloc/tokio-postgres/tower-http/bytes/http/http-body-util/tower) to their resolved versions, per the all-versions-fully-specced rule. kube 4.0 is a major release: this is compile- and unit-clean, but the integration suite (CI) should validate runtime behaviour (watchers, events, patches) before merge.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤖 What was holding back k8s-openapi 0.28: kube 3.1 pins k8s-openapi
^0.27, so bumping k8s-openapi requires kube 4.0 (which requires^0.28). It's the kube 3→4 major bump under the hood.Pleasant surprise: it's dependency-only for pgro — no source
changes.
cargo check --all-targets,clippy -D warnings, and the unitsuite (171 tests) all pass unchanged.
kube_quantity 0.9's loosek8s-openapi (
^0) unifies onto 0.28.Also fully-specs the remaining loose dependency versions
(
mimalloc/tokio-postgres/tower-http/bytes/http/http-body-util/tower)to their resolved versions, per the all-versions-fully-specced rule.
Caveat
kube 4.0 is a major release. This is compile- and unit-clean, but a
major bump can shift runtime behaviour (watcher semantics, events API,
patch handling) that unit tests don't exercise — the integration suite
(CI) should go green before merge.
Independent of the canopy stack (#87/#88); branches off
main.