chore(deps): bump fabric8-client.version from 6.12.1 to 6.13.1
Bumps fabric8-client.version from 6.12.1 to 6.13.1.
Updates io.fabric8:kubernetes-client-bom from 6.12.1 to 6.13.1
Release notes
Sourced from io.fabric8:kubernetes-client-bom's releases.
6.13.1 (2024-07-02)
Bugs
- Fix #6059: Swallow rejected execution from internal usage of the informer executor
- Fix #6068: KubernetesMockServer provides incomplete Configuration while creating test Config for KubernetesClient
- Fix #6085: model getters have same annotations as fields (breaks native)
Full Changelog: https://github.com/fabric8io/kubernetes-client/compare/v6.13.0...v6.13.1
6.13.0 (2024-05-29)
Bugs
- Fix #5866: Addressed cycle in crd generation with Java 19+ and ZonedDateTime
- Fix #5960: The serialization of time related types should be string
Improvements
- Fix #5605: proxy configs support proxy URLs without a scheme
- Fix #5867: (crd-generator) Imply schemaFrom via JsonFormat shape (SchemaFrom takes precedence)
- Fix #5867: (java-generator) Add JsonFormat shape to date-time
- Fix #5878: (java-generator) Add implements Editable for extraAnnotations
- Fix #5878: (java-generator) Update documentation to include dependencies
- Fix #5953: Made informer watch starting deterministic with respect to list processing
- Fix #5954: (crd-generator) Sort required properties to ensure deterministic output
- Fix #5973: CacheImpl locking for reading indexes (Cache.byIndex|indexKeys|index) was reduced
- Fix #6012: Add convenience methods on HasMetadata to help with SSA
Dependency Upgrade
- Fix #5695: Upgrade Fabric8 Kubernetes Model to Kubernetes v1.30.0
Note: Breaking changes
- Fix #5947: CRD generation using the v1beta1 version is deprecated. Please use only v1 instead.
- Fix #5960: The KubernetesSerializer will now by default serialize time related types to strings - rather than object, integer, number, or arrays of integer / number. If you are using these types in a custom object and were not including JsonFormat annotations to adjust the serialization they were likely being serialized in a non-standard way that would not be usable other Kubernetes clients, nor match the generated custom resource definition if one was being produced. Please open an issue if you need the previous behavior for whatever reason - there is a workaround by creating a customized KubernetesSerializer.
storagemigration.k8s.io/v1alpha1StorageVersionMigrationintroduced in Kubernetes 1.30.0 is added to kubernetes-model-storageclass module. A dedicated module hasn't been created for this new ApiGroup.- Fix #6006: Service Catalog extension is deprecated following its deprecation in Kubernetes.
New Contributors
@wind57made their first contribution in fabric8io/kubernetes-client#5937Full Changelog: https://github.com/fabric8io/kubernetes-client/compare/v6.12.1...v6.13.0
Changelog
Sourced from io.fabric8:kubernetes-client-bom's changelog.
6.13.1 (2024-07-02)
Bugs
- Fix #6059: Swallow rejected execution from internal usage of the informer executor
- Fix #6068: KubernetesMockServer provides incomplete Configuration while creating test Config for KubernetesClient
- Fix #6085: model getters have same annotations as fields (breaks native)
6.13.0 (2024-05-29)
Bugs
- Fix #5866: Addressed cycle in crd generation with Java 19+ and ZonedDateTime
- Fix #5960: The serialization of time related types should be string
Improvements
- Fix #5605: proxy configs support proxy URLs without a scheme
- Fix #5867: (crd-generator) Imply schemaFrom via JsonFormat shape (SchemaFrom takes precedence)
- Fix #5867: (java-generator) Add JsonFormat shape to date-time
- Fix #5878: (java-generator) Add implements Editable for extraAnnotations
- Fix #5878: (java-generator) Update documentation to include dependencies
- Fix #5953: Made informer watch starting deterministic with respect to list processing
- Fix #5954: (crd-generator) Sort required properties to ensure deterministic output
- Fix #5973: CacheImpl locking for reading indexes (Cache.byIndex|indexKeys|index) was reduced
- Fix #6012: Add convenience methods on HasMetadata to help with SSA
Dependency Upgrade
- Fix #5695: Upgrade Fabric8 Kubernetes Model to Kubernetes v1.30.0
Note: Breaking changes
- Fix #5947: CRD generation using the v1beta1 version is deprecated. Please use only v1 instead.
- Fix #5960: The KubernetesSerializer will now by default serialize time related types to strings - rather than object, integer, number, or arrays of integer / number. If you are using these types in a custom object and were not including JsonFormat annotations to adjust the serialization they were likely being serialized in a non-standard way that would not be usable other Kubernetes clients, nor match the generated custom resource definition if one was being produced. Please open an issue if you need the previous behavior for whatever reason - there is a workaround by creating a customized KubernetesSerializer.
storagemigration.k8s.io/v1alpha1StorageVersionMigrationintroduced in Kubernetes 1.30.0 is added to kubernetes-model-storageclass module. A dedicated module hasn't been created for this new ApiGroup.- Fix #6006: Service Catalog extension is deprecated following its deprecation in Kubernetes.
Commits
33181b8[RELEASE] Updated project version to v6.13.183d47befix: generated classes handle java.lang.String type consistently (6094)762929cfix: don't add apiVersion,kind,metadata fields indiscriminately to JsonProper...1da2affModel getters have same annotations as fields (breaks native) (6086)34d3744fix(mock-server): KubernetesMockServer provides a valid, complete configurati...d264884fix: swallow rejected execution after shutdown91c7f77[RELEASE] Updated project version to v6.13.0c2a5ba4chore(deps): bump org.sonatype.plugins:nexus-staging-maven-plugine0647d7feat: add factory methods to help with SSA (6013)52ccd57chore(deps): bump org.apache.maven:maven-core from 3.9.6 to 3.9.7- Additional commits viewable in compare view
Updates io.fabric8:kubernetes-server-mock from 6.12.1 to 6.13.1
Updates io.fabric8:openshift-client from 6.12.1 to 6.13.1
Release notes
Sourced from io.fabric8:openshift-client's releases.
6.13.1 (2024-07-02)
Bugs
- Fix #6059: Swallow rejected execution from internal usage of the informer executor
- Fix #6068: KubernetesMockServer provides incomplete Configuration while creating test Config for KubernetesClient
- Fix #6085: model getters have same annotations as fields (breaks native)
Full Changelog: https://github.com/fabric8io/kubernetes-client/compare/v6.13.0...v6.13.1
6.13.0 (2024-05-29)
Bugs
- Fix #5866: Addressed cycle in crd generation with Java 19+ and ZonedDateTime
- Fix #5960: The serialization of time related types should be string
Improvements
- Fix #5605: proxy configs support proxy URLs without a scheme
- Fix #5867: (crd-generator) Imply schemaFrom via JsonFormat shape (SchemaFrom takes precedence)
- Fix #5867: (java-generator) Add JsonFormat shape to date-time
- Fix #5878: (java-generator) Add implements Editable for extraAnnotations
- Fix #5878: (java-generator) Update documentation to include dependencies
- Fix #5953: Made informer watch starting deterministic with respect to list processing
- Fix #5954: (crd-generator) Sort required properties to ensure deterministic output
- Fix #5973: CacheImpl locking for reading indexes (Cache.byIndex|indexKeys|index) was reduced
- Fix #6012: Add convenience methods on HasMetadata to help with SSA
Dependency Upgrade
- Fix #5695: Upgrade Fabric8 Kubernetes Model to Kubernetes v1.30.0
Note: Breaking changes
- Fix #5947: CRD generation using the v1beta1 version is deprecated. Please use only v1 instead.
- Fix #5960: The KubernetesSerializer will now by default serialize time related types to strings - rather than object, integer, number, or arrays of integer / number. If you are using these types in a custom object and were not including JsonFormat annotations to adjust the serialization they were likely being serialized in a non-standard way that would not be usable other Kubernetes clients, nor match the generated custom resource definition if one was being produced. Please open an issue if you need the previous behavior for whatever reason - there is a workaround by creating a customized KubernetesSerializer.
storagemigration.k8s.io/v1alpha1StorageVersionMigrationintroduced in Kubernetes 1.30.0 is added to kubernetes-model-storageclass module. A dedicated module hasn't been created for this new ApiGroup.- Fix #6006: Service Catalog extension is deprecated following its deprecation in Kubernetes.
New Contributors
@wind57made their first contribution in fabric8io/kubernetes-client#5937Full Changelog: https://github.com/fabric8io/kubernetes-client/compare/v6.12.1...v6.13.0
Changelog
Sourced from io.fabric8:openshift-client's changelog.
6.13.1 (2024-07-02)
Bugs
- Fix #6059: Swallow rejected execution from internal usage of the informer executor
- Fix #6068: KubernetesMockServer provides incomplete Configuration while creating test Config for KubernetesClient
- Fix #6085: model getters have same annotations as fields (breaks native)
6.13.0 (2024-05-29)
Bugs
- Fix #5866: Addressed cycle in crd generation with Java 19+ and ZonedDateTime
- Fix #5960: The serialization of time related types should be string
Improvements
- Fix #5605: proxy configs support proxy URLs without a scheme
- Fix #5867: (crd-generator) Imply schemaFrom via JsonFormat shape (SchemaFrom takes precedence)
- Fix #5867: (java-generator) Add JsonFormat shape to date-time
- Fix #5878: (java-generator) Add implements Editable for extraAnnotations
- Fix #5878: (java-generator) Update documentation to include dependencies
- Fix #5953: Made informer watch starting deterministic with respect to list processing
- Fix #5954: (crd-generator) Sort required properties to ensure deterministic output
- Fix #5973: CacheImpl locking for reading indexes (Cache.byIndex|indexKeys|index) was reduced
- Fix #6012: Add convenience methods on HasMetadata to help with SSA
Dependency Upgrade
- Fix #5695: Upgrade Fabric8 Kubernetes Model to Kubernetes v1.30.0
Note: Breaking changes
- Fix #5947: CRD generation using the v1beta1 version is deprecated. Please use only v1 instead.
- Fix #5960: The KubernetesSerializer will now by default serialize time related types to strings - rather than object, integer, number, or arrays of integer / number. If you are using these types in a custom object and were not including JsonFormat annotations to adjust the serialization they were likely being serialized in a non-standard way that would not be usable other Kubernetes clients, nor match the generated custom resource definition if one was being produced. Please open an issue if you need the previous behavior for whatever reason - there is a workaround by creating a customized KubernetesSerializer.
storagemigration.k8s.io/v1alpha1StorageVersionMigrationintroduced in Kubernetes 1.30.0 is added to kubernetes-model-storageclass module. A dedicated module hasn't been created for this new ApiGroup.- Fix #6006: Service Catalog extension is deprecated following its deprecation in Kubernetes.
Commits
33181b8[RELEASE] Updated project version to v6.13.183d47befix: generated classes handle java.lang.String type consistently (6094)762929cfix: don't add apiVersion,kind,metadata fields indiscriminately to JsonProper...1da2affModel getters have same annotations as fields (breaks native) (6086)34d3744fix(mock-server): KubernetesMockServer provides a valid, complete configurati...d264884fix: swallow rejected execution after shutdown91c7f77[RELEASE] Updated project version to v6.13.0c2a5ba4chore(deps): bump org.sonatype.plugins:nexus-staging-maven-plugine0647d7feat: add factory methods to help with SSA (6013)52ccd57chore(deps): bump org.apache.maven:maven-core from 3.9.6 to 3.9.7- Additional commits viewable in compare view
Updates io.fabric8:crd-generator-apt from 6.12.1 to 6.13.1
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
-
@dependabot rebasewill rebase this PR -
@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it -
@dependabot mergewill merge this PR after your CI passes on it -
@dependabot squash and mergewill squash and merge this PR after your CI passes on it -
@dependabot cancel mergewill cancel a previously requested merge and block automerging -
@dependabot reopenwill reopen this PR if it is closed -
@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency -
@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) -
@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)