chore: update rust crate k8s-openapi to 0.23 #3

renovate · 2022-06-23T19:10:45Z

This PR contains the following updates:

Package	Type	Update	Change
k8s-openapi	dev-dependencies	minor	`0.14` -> `0.23`
k8s-openapi	dependencies	minor	`0.14` -> `0.23`

Release Notes

Arnavion/k8s-openapi (k8s-openapi)

`v0.23.0`

Compare Source

k8s-openapi

BREAKING CHANGE: Added support for Kubernetes 1.31 under the v1_31 feature.
BREAKING CHANGE: Dropped support for Kubernetes 1.24 and 1.25.

Corresponding Kubernetes API server versions:

v1.26.15
v1.27.16
v1.28.14
v1.29.9
v1.30.5
v1.31.1

k8s-openapi-codegen-common

No changes.

k8s-openapi-derive

No changes except to bump the k8s-openapi-codegen-common dependency to the new version.

`v0.22.0`

Compare Source

k8s-openapi

BREAKING CHANGE: Added support for Kubernetes 1.30 under the v1_30 feature.

Corresponding Kubernetes API server versions:

v1.24.17
v1.25.16
v1.26.15
v1.27.13
v1.28.9
v1.29.4
v1.30.0

k8s-openapi-codegen-common

No changes.

k8s-openapi-derive

No changes except to bump the k8s-openapi-codegen-common dependency to the new version.

`v0.21.1`

Compare Source

k8s-openapi

BUGFIX: Fix schemars::JsonSchema impl of k8s_openapi::apimachinery::pkg::util::intstr::IntOrString to be in line with what Kubernetes expects of int-or-string fields in CRDs.

Corresponding Kubernetes API server versions:

v1.24.17
v1.25.16
v1.26.14
v1.27.11
v1.28.7
v1.29.2

k8s-openapi-codegen-common

BUGFIX: See the bugfix mentioned above.

k8s-openapi-derive

No changes except to bump the k8s-openapi-codegen-common dependency to the new version.

`v0.21.0`

Compare Source

k8s-openapi

BREAKING CHANGE: Added support for Kubernetes 1.29 under the v1_29 feature.
BREAKING CHANGE: Dropped support for Kubernetes 1.22 and 1.23.

Corresponding Kubernetes API server versions:

v1.24.17
v1.25.16
v1.26.13
v1.27.10
v1.28.6
v1.29.1

k8s-openapi-codegen-common

No changes.

k8s-openapi-derive

No changes.

`v0.20.0`

Compare Source

k8s-openapi

BREAKING CHANGE: This release removes all associated methods of resource types that mapped API operations. For example, there is no more fn api::core::v1::Pod::list(), and all types related to API operations like ListOptional and ResponseBody have also been removed. See https://github.com/Arnavion/k8s-openapi/issues/149 for more details.
BREAKING CHANGE: Added support for Kubernetes 1.28 under the v1_28 feature.
BREAKING CHANGE: Dropped support for Kubernetes 1.20 and 1.21.

Corresponding Kubernetes API server versions:

v1.22.17
v1.23.17
v1.24.17
v1.25.13
v1.26.8
v1.27.5
v1.28.1

k8s-openapi-codegen-common

BREAKING CHANGE: write_operation and other things related to emitting API operations have been removed.

k8s-openapi-derive

BREAKING CHANGE: The generated resource type no longer has associated clientset methods for listing etc.

`v0.19.0`

Compare Source

k8s-openapi

BREAKING CHANGE: Added support for Kubernetes 1.27 under the v1_27 feature.
FEATURE: The k8s-openapi now has two additional Cargo features earliest and latest, which select the earliest and latest supported version. For example, in this release, earliest is equivalent to v1_20 and latest is equivalent to v1_27.

Corresponding Kubernetes API server versions:

v1.20.15
v1.21.14
v1.22.17
v1.23.17
v1.24.16
v1.25.12
v1.26.7
v1.27.4

k8s-openapi-codegen-common

No changes.

k8s-openapi-derive

No changes.

`v0.18.0`

Compare Source

k8s-openapi

BREAKING CHANGE: The k8s_openapi::DeepMerge trait and its impls on this crate's types now have semantics in line with merge strategies in Kubernetes. Specifically, the code generator now takes the x-kubernetes-list-map-keys, x-kubernetes-list-type, x-kubernetes-map-type, x-kubernetes-patch-merge-key and x-kubernetes-patch-strategy annotations into account when generating the DeepMerge impls.

For example, in v0.17.0, PodSpec::merge_from would append entries into self.containers, whereas now it does a "list-map" strategy to replace containers with the same name.

Corresponding Kubernetes API server versions:

v1.20.15
v1.21.14
v1.22.17
v1.23.17
v1.24.12
v1.25.8
v1.26.3

k8s-openapi-codegen-common

BREAKING CHANGE: As mentioned above, the generated code for k8s_openapi::DeepMerge impls now takes merge strategy annotations into account.

k8s-openapi-derive

No changes.

`v0.17.0`

Compare Source

k8s-openapi

BREAKING CHANGE: Added support for Kubernetes 1.26 under the v1_26 feature.
BREAKING CHANGE: Dropped support for Kubernetes 1.18 and 1.19.
FEATURE: Allow deserializing non-optional ByteStrings from JSON null. The API server is known to allow these nulls in the ConfigMap::binary_data and Secret::data maps. The deserialization results in an empty ByteString, to match the behavior of the API server when given a null value in the ConfigMap::data map.

Corresponding Kubernetes API server versions:

v1.20.15
v1.21.14
v1.22.17
v1.23.15
v1.24.9
v1.25.5
v1.26.0

k8s-openapi-codegen-common

No changes.

k8s-openapi-derive

No changes.

`v0.16.0`

Compare Source

k8s-openapi

BREAKING CHANGE: Added support for Kubernetes 1.25 under the v1_25 feature.
FEATURE: All spec types now implement a deep-merge API via a DeepMerge trait impl with a fn merge_from(&mut self, other: Self) method. This is useful for builder-like operations.

Corresponding Kubernetes API server versions:

v1.18.20
v1.19.16
v1.20.15
v1.21.14
v1.22.14
v1.23.11
v1.24.5
v1.25.1

k8s-openapi-codegen-common

No changes.

k8s-openapi-derive

BREAKING CHANGE: #[derive(CustomResourceDefinition)] no longer generates a list type alias. For example, when applied to struct FooSpec, previously the custom derive would generate pub type FooList = k8s_openapi::List<Foo>; It no longer does this, in accordance with the main k8s-openapi crate where such aliases were removed back in v0.7.0
FEATURE: The generated custom resource type will implement k8s_openapi::DeepMerge if the impl_deep_merge custom derive attribute is used. Note that this requires you to implement k8s_openapi::DeepMerge on the spec type yourself; the custom derive does not do that.

`v0.15.0`

Compare Source

k8s-openapi

BREAKING CHANGE: The pretty optional parameter has been removed from all operations. Setting this parameter to true would've made the API server pretty-print the JSON response, which is meaningless for a programmatic client.
BREAKING CHANGE: In addition to the previous change, the exact and export parameters have been removed from all read operations (eg Pod::read_namespaced_pod). These parameters were removed in Kubernetes v1.21 and were known to be broken before that, and would've caused the server response to not be able to be parsed correctly via the operation's response type anyway.

All read operations with the exception of Pod::read_namespaced_pod_log had only these three optional parameters, so now that they've been removed such read operations don't have an optional: ReadFooOptional<'_> parameter at all.
BREAKING CHANGE: Operation names no longer include the _namespaced part and the resource type name. For example, Pod::read_namespaced_pod is now just Pod::read. The corresponding optional parameters type and response type no longer include the Namespaced part, eg ReadNamespacedPodResponse is now just ReadPodResponse.
BREAKING CHANGE: Added support for Kubernetes 1.24 under the v1_24 feature.
BREAKING CHANGE: Dropped support for Kubernetes 1.16 and 1.17.
FEATURE: The K8S_OPENAPI_ENABLED_VERSION env var can now be set at build time to enable a specific API version, just like enabling a specific version feature would've done. This is only meant to be used by library developers who want to run cargo check, cargo doc, etc commands, for which the previous advice of enabling a version feature via a dev dependency would not work.

Corresponding Kubernetes API server versions:

v1.18.20
v1.19.16
v1.20.15
v1.21.12
v1.22.9
v1.23.6
v1.24.0

k8s-openapi-codegen-common

No changes.

k8s-openapi-derive

No changes.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

renovate · 2023-09-08T02:56:22Z

⚠ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path libs/utils/cops/Cargo.toml --workspace
warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest
note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest
note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions
    Updating crates.io index
error: failed to select a version for `k8s-openapi`.
    ... required by package `fluxcd-meta v0.0.0 (/tmp/renovate/repos/github/YoloDev/rust-fluxcd/libs/meta)`
versions that meet the requirements `^0.22` are: 0.22.0

the package `fluxcd-meta` depends on `k8s-openapi`, with features: `v1_21` but `k8s-openapi` does not have these features.


failed to select a version for `k8s-openapi` which could resolve this conflict

File name: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path libs/utils/cap/Cargo.toml --workspace
warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest
note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest
note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions
    Updating crates.io index
error: failed to select a version for `k8s-openapi`.
    ... required by package `fluxcd-meta v0.0.0 (/tmp/renovate/repos/github/YoloDev/rust-fluxcd/libs/meta)`
versions that meet the requirements `^0.22` are: 0.22.0

the package `fluxcd-meta` depends on `k8s-openapi`, with features: `v1_21` but `k8s-openapi` does not have these features.


failed to select a version for `k8s-openapi` which could resolve this conflict

File name: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path libs/meta/Cargo.toml --workspace
warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest
note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest
note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions
    Updating crates.io index
error: failed to select a version for `k8s-openapi`.
    ... required by package `fluxcd-meta v0.0.0 (/tmp/renovate/repos/github/YoloDev/rust-fluxcd/libs/meta)`
versions that meet the requirements `^0.22` are: 0.22.0

the package `fluxcd-meta` depends on `k8s-openapi`, with features: `v1_21` but `k8s-openapi` does not have these features.


failed to select a version for `k8s-openapi` which could resolve this conflict

File name: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path libs/acl/Cargo.toml --workspace
warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest
note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest
note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions
    Updating crates.io index
error: failed to select a version for `k8s-openapi`.
    ... required by package `fluxcd-meta v0.0.0 (/tmp/renovate/repos/github/YoloDev/rust-fluxcd/libs/meta)`
versions that meet the requirements `^0.22` are: 0.22.0

the package `fluxcd-meta` depends on `k8s-openapi`, with features: `v1_21` but `k8s-openapi` does not have these features.


failed to select a version for `k8s-openapi` which could resolve this conflict

File name: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path controllers/source/github-keys/Cargo.toml --workspace
warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest
note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest
note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions
    Updating crates.io index
error: failed to select a version for `k8s-openapi`.
    ... required by package `fluxcd-meta v0.0.0 (/tmp/renovate/repos/github/YoloDev/rust-fluxcd/libs/meta)`
versions that meet the requirements `^0.22` are: 0.22.0

the package `fluxcd-meta` depends on `k8s-openapi`, with features: `v1_21` but `k8s-openapi` does not have these features.


failed to select a version for `k8s-openapi` which could resolve this conflict

File name: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path api/source/github-keys/Cargo.toml --workspace
warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest
note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest
note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions
    Updating crates.io index
error: failed to select a version for `k8s-openapi`.
    ... required by package `fluxcd-meta v0.0.0 (/tmp/renovate/repos/github/YoloDev/rust-fluxcd/libs/meta)`
versions that meet the requirements `^0.22` are: 0.22.0

the package `fluxcd-meta` depends on `k8s-openapi`, with features: `v1_21` but `k8s-openapi` does not have these features.


failed to select a version for `k8s-openapi` which could resolve this conflict

renovate · 2024-09-16T14:58:55Z

⚠️ Artifact update problem

Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path api/source/github-keys/Cargo.toml --workspace
warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest
note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest
note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions
    Updating crates.io index
error: failed to select a version for `k8s-openapi`.
    ... required by package `fluxcd-meta v0.0.0 (/tmp/renovate/repos/github/YoloDev/rust-fluxcd/libs/meta)`
versions that meet the requirements `^0.23` are: 0.23.0

the package `fluxcd-meta` depends on `k8s-openapi`, with features: `v1_21` but `k8s-openapi` does not have these features.


failed to select a version for `k8s-openapi` which could resolve this conflict

File name: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path controllers/source/github-keys/Cargo.toml --workspace
warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest
note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest
note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions
    Updating crates.io index
error: failed to select a version for `k8s-openapi`.
    ... required by package `fluxcd-meta v0.0.0 (/tmp/renovate/repos/github/YoloDev/rust-fluxcd/libs/meta)`
versions that meet the requirements `^0.23` are: 0.23.0

the package `fluxcd-meta` depends on `k8s-openapi`, with features: `v1_21` but `k8s-openapi` does not have these features.


failed to select a version for `k8s-openapi` which could resolve this conflict

File name: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path libs/acl/Cargo.toml --workspace
warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest
note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest
note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions
    Updating crates.io index
error: failed to select a version for `k8s-openapi`.
    ... required by package `fluxcd-meta v0.0.0 (/tmp/renovate/repos/github/YoloDev/rust-fluxcd/libs/meta)`
versions that meet the requirements `^0.23` are: 0.23.0

the package `fluxcd-meta` depends on `k8s-openapi`, with features: `v1_21` but `k8s-openapi` does not have these features.


failed to select a version for `k8s-openapi` which could resolve this conflict

File name: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path libs/meta/Cargo.toml --workspace
warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest
note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest
note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions
    Updating crates.io index
error: failed to select a version for `k8s-openapi`.
    ... required by package `fluxcd-meta v0.0.0 (/tmp/renovate/repos/github/YoloDev/rust-fluxcd/libs/meta)`
versions that meet the requirements `^0.23` are: 0.23.0

the package `fluxcd-meta` depends on `k8s-openapi`, with features: `v1_21` but `k8s-openapi` does not have these features.


failed to select a version for `k8s-openapi` which could resolve this conflict

File name: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path libs/utils/cap/Cargo.toml --workspace
warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest
note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest
note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions
    Updating crates.io index
error: failed to select a version for `k8s-openapi`.
    ... required by package `fluxcd-meta v0.0.0 (/tmp/renovate/repos/github/YoloDev/rust-fluxcd/libs/meta)`
versions that meet the requirements `^0.23` are: 0.23.0

the package `fluxcd-meta` depends on `k8s-openapi`, with features: `v1_21` but `k8s-openapi` does not have these features.


failed to select a version for `k8s-openapi` which could resolve this conflict

File name: Cargo.lock

Command failed: cargo update --config net.git-fetch-with-cli=true --manifest-path libs/utils/cops/Cargo.toml --workspace
warning: virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
note: to keep the current resolver, specify `workspace.resolver = "1"` in the workspace root's manifest
note: to use the edition 2021 resolver, specify `workspace.resolver = "2"` in the workspace root's manifest
note: for more details see https://doc.rust-lang.org/cargo/reference/resolver.html#resolver-versions
    Updating crates.io index
error: failed to select a version for `k8s-openapi`.
    ... required by package `fluxcd-meta v0.0.0 (/tmp/renovate/repos/github/YoloDev/rust-fluxcd/libs/meta)`
versions that meet the requirements `^0.23` are: 0.23.0

the package `fluxcd-meta` depends on `k8s-openapi`, with features: `v1_21` but `k8s-openapi` does not have these features.


failed to select a version for `k8s-openapi` which could resolve this conflict

renovate bot added automerge dependencies labels Jun 23, 2022

renovate bot force-pushed the renovate/k8s-openapi-0.x branch from 810c44f to 28522b2 Compare September 25, 2022 21:58

renovate bot changed the title ~~chore: update rust crate k8s-openapi to 0.15~~ chore: update rust crate k8s-openapi to 0.16 Nov 20, 2022

renovate bot force-pushed the renovate/k8s-openapi-0.x branch from 28522b2 to f5a8cfd Compare March 18, 2023 22:13

renovate bot changed the title ~~chore: update rust crate k8s-openapi to 0.16~~ chore: update rust crate k8s-openapi to 0.17 Mar 18, 2023

renovate bot force-pushed the renovate/k8s-openapi-0.x branch from f5a8cfd to 186bc64 Compare May 29, 2023 22:01

renovate bot changed the title ~~chore: update rust crate k8s-openapi to 0.17~~ chore: update rust crate k8s-openapi to 0.18 May 29, 2023

renovate bot changed the title ~~chore: update rust crate k8s-openapi to 0.18~~ chore: update rust crate k8s-openapi to 0.19 Aug 6, 2023

renovate bot force-pushed the renovate/k8s-openapi-0.x branch from 186bc64 to 669cd78 Compare August 6, 2023 02:05

renovate bot force-pushed the renovate/k8s-openapi-0.x branch from 669cd78 to a4ed9cd Compare September 8, 2023 02:56

renovate bot changed the title ~~chore: update rust crate k8s-openapi to 0.19~~ chore: update rust crate k8s-openapi to 0.20 Sep 8, 2023

renovate bot force-pushed the renovate/k8s-openapi-0.x branch from a4ed9cd to a46e540 Compare January 20, 2024 11:43

renovate bot changed the title ~~chore: update rust crate k8s-openapi to 0.20~~ chore: update rust crate k8s-openapi to 0.21 Jan 20, 2024

renovate bot force-pushed the renovate/k8s-openapi-0.x branch from a46e540 to 0fd49ff Compare May 5, 2024 02:49

renovate bot changed the title ~~chore: update rust crate k8s-openapi to 0.21~~ chore: update rust crate k8s-openapi to 0.22 May 5, 2024

chore: update rust crate k8s-openapi to 0.23

749dd28

renovate bot force-pushed the renovate/k8s-openapi-0.x branch from 0fd49ff to 749dd28 Compare September 16, 2024 14:58

renovate bot changed the title ~~chore: update rust crate k8s-openapi to 0.22~~ chore: update rust crate k8s-openapi to 0.23 Sep 16, 2024

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

chore: update rust crate k8s-openapi to 0.23 #3

chore: update rust crate k8s-openapi to 0.23 #3

renovate bot commented Jun 23, 2022 •

edited

Loading

renovate bot commented Sep 8, 2023 •

edited

Loading

renovate bot commented Sep 16, 2024

chore: update rust crate k8s-openapi to 0.23 #3

Are you sure you want to change the base?

chore: update rust crate k8s-openapi to 0.23 #3

Conversation

renovate bot commented Jun 23, 2022 • edited Loading

Release Notes

k8s-openapi

k8s-openapi-codegen-common

k8s-openapi-derive

k8s-openapi

k8s-openapi-codegen-common

k8s-openapi-derive

k8s-openapi

k8s-openapi-codegen-common

k8s-openapi-derive

k8s-openapi

k8s-openapi-codegen-common

k8s-openapi-derive

k8s-openapi

k8s-openapi-codegen-common

k8s-openapi-derive

k8s-openapi

k8s-openapi-codegen-common

k8s-openapi-derive

k8s-openapi

k8s-openapi-codegen-common

k8s-openapi-derive

k8s-openapi

k8s-openapi-codegen-common

k8s-openapi-derive

k8s-openapi

k8s-openapi-codegen-common

k8s-openapi-derive

k8s-openapi

k8s-openapi-codegen-common

k8s-openapi-derive

Configuration

renovate bot commented Sep 8, 2023 • edited Loading

⚠ Artifact update problem

File name: Cargo.lock

File name: Cargo.lock

File name: Cargo.lock

File name: Cargo.lock

File name: Cargo.lock

File name: Cargo.lock

renovate bot commented Sep 16, 2024

⚠️ Artifact update problem

File name: Cargo.lock

File name: Cargo.lock

File name: Cargo.lock

File name: Cargo.lock

File name: Cargo.lock

File name: Cargo.lock

renovate bot commented Jun 23, 2022 •

edited

Loading

renovate bot commented Sep 8, 2023 •

edited

Loading