chore(deps): update dependency kind to v0.32.0 - autoclosed #36

2026-09-27T00:08:58Z

gitea_admin commented

2026-09-27 00:08:58 +00:00

This PR contains the following updates:

Package	Update	Change
kind	minor	`0.29.0` → `0.32.0`

Release Notes

kubernetes-sigs/kind (kind)

`v0.32.0`

This release contains critical dependency updates, bug fixes, and defaults to Kubernetes 1.36.1.

Breaking Changes

The default node image is now kindest/node:v1.36.1@sha256:3489c7674813ba5d8b1a9977baea8a6e553784dab7b84759d1014dbd78f7ebd5
New node images requiring upgrading kind to kind load ...: Due to a containerd upgrade, you must upgrade kind to this release or newer to use kind load ... with the newly published node images. As always, we cannot gurantee full compatibility of node images between kind releases. You can use the digests from previous releases, upgrade kind, or build your own node-images.
kubeadm v1beta4 config format is now used for Kubernetes 1.36.0+ If you are using versioned config patches, you must update to target v1beta4. Unversioned patches kind will attempt to convert as needed (more below in New Features). This change is required for Kubernetes 1.37+ which drops kubeadm v1beta3 config.
Adoption of Envoy for Load Balancing in multi-control-plane node clusters: HAProxy has been replaced by Envoy (docker.io/envoyproxy/envoy:v1.36.2) as the load balancer in multi-control-plane (HA) clusters. If you rely on custom HAProxy loadbalancer configurations or images, please note that Envoy is now used.
cgroup v1 warning: A warning is now printed if cgroup v1 is detected on the host. Kubernetes has deprecated support for cgroup v1, and at some point in the future KIND releases / node-images will also drop support for cgroup v1.

New Features

kubeadm v1beta4 configuration support: KIND now uses the v1beta4 config format for Kubernetes v1.36.0+ while maintaining v1beta3 for v1.23.0 up to v1.35.x, and v1beta2 for older versions.
Custom Merging & Version-Awareness for Kubeadm Config Patches:
- KIND now automatically translates old-style map-based extraArgs / kubeletExtraArgs patches to the list-based v1beta4 format when targeting v1beta4 configs.
- Config patches now append to extraArgs / kubeletExtraArgs / certSANs reliably. To overwrite or make other more precise patching, use json6902 patches.
Support for containerd config v4 format: Enabled support for containerd's config v4 format in kind load and snapshotter parsing, which is required for newer containerd versions.
Building Node Images from CI Artifacts: Added support to build node images from Kubernetes CI artifacts (resolving endpoints like https://dl.k8s.io/ci/latest.txt or CI build prefixes).
Support for containerd version-aware containerd config patching: Like kubeadmConfigPatches, containerd config patching is now aware of version and if specified in patches will only apply patches that match the containerd config being used.
Assorted dependency updates.

Images pre-built for this release:

v1.36.1: kindest/node:v1.36.1@sha256:3489c7674813ba5d8b1a9977baea8a6e553784dab7b84759d1014dbd78f7ebd5
v1.35.5: kindest/node:v1.35.5@sha256:ce977ae6d65918d0b58a5f8b5e940429c2ce42fa3a5619ec2bbc60b949c0ac95
v1.34.8: kindest/node:v1.34.8@sha256:02722c2dedddcfc00febf5d27fbeb9b7b2c14294c82109ff4a85d89ac9ba3256
v1.33.12: kindest/node:v1.33.12@sha256:3f5c8443c620245e4d355cfe09e96a91ead32ceaa569d3f1ca9edf0cb2fe2ff4

NOTE: You must use the @sha256 digest to guarantee an image built for this release, until such a time as we switch to a different tagging scheme. Even then we will highly encourage digest pinning for security and reproducibility reasons.

Fixes

Fix permission error when creating pods with hostUsers: false (Kubernetes 1.36+).
Handle registry ports correctly in image normalization logic (e.g., registry running on ports like localhost:5000/...).
Handle empty port mapping listen addresses correctly (defaults to wildcard address).
Skip /dev/mapper mount on rootless Docker.
Assorted documentation fixes and improvements.

Contributors

Committers for this release:

We'd also like to thank everyone who touched the codebase, filed issues, and helped the community!

`v0.31.0`

This release contains dependency updates and defaults to Kubernetes 1.35.0.

Please take note of the breaking changes from Kubernetes 1.35, and how to prepare for future changes to move off of the deprecated kubeam v1beta3 in favor of v1beta4. We will include updated reminders for both again in subsequent releases.

Breaking Changes

The default node image is now kindest/node:v1.35.0@sha256:452d707d4862f52530247495d180205e029056831160e22870e37e3f6c1ac31f

Kubernetes 1.35+ Cgroup v1

Kubernetes will be removing cgroup v1 support, and therefore kind node images at those versions will also be dropping support.

You can read more about this change in the Kubernetes release blog: https://kubernetes.io/blog/2025/12/17/kubernetes-v1-35-release/#removal-of-cgroup-v1-support

If you must use kind on cgroup v1, we recommend using an older Kubernetes release for the immediate future, but we also strongly recommend migrating to cgroup v2.

In the near future as Kubernetes support dwindles, KIND will also clean up cgroup v1 workarounds and drop support in future kind releases and images, regardless of Kubernetes version.

Most stable linux distros should be on cgroupv2 out of the box.

This is a reminder to use pinned images by digest, see the note below about images for this release.

Kubeadm Config Future Breaking Change

WARNING: Future kind releases will adopt kubeadm v1beta4 configuration, kubeadm v1beta4 has a breaking change to extraArgs: https://kubernetes.io/blog/2024/08/23/kubernetes-1-31-kubeadm-v1beta4/.

If you use the kubeadmConfigPatches feature then you may need to prepare for this change.
We recommend that you use versioned config patches that explicitly match the version required.

KIND uses kubeadm v1beta3 for Kubernetes 1.23+, and will likely use v1beta4 for Kubernetes 1.36+
The exact version is TBD pending work to fix this but expected to be 1.36.
It will definitely be an as-of-yet-unreleased Kubernetes version to avoid surprises, and it will not be on a patch-release boundary.

KIND may still work with older Kubernetes versions at v1beta2, but we no longer test or actively support these as Kubernetes only supports 1.32+ currently: https://kubernetes.io/releases/

You likely only need v1beta3 + v1beta4 patches, you can take your existing patches that work with v1beta3, explicitly set apiVersion: kubeadm.k8s.io/v1beta3 in the patch at the top level, and make another copy for v1beta4. The v1beta4 patch will need to move extraArgs from a map to a list, for examples see: https://kubernetes.io/docs/reference/config-api/kubeadm-config.v1beta4/

For a concrete example of kind config with kubeadm config patch targeting both v1beta3 and v1beta4, consider this simple kind config that sets verbosity of the apiserver logs:

kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
kubeadmConfigPatches:

# patch for v1beta3 (1.23 ...)
- |
  kind: ClusterConfiguration
  apiVersion: kubeadm.k8s.io/v1beta3
  apiServer:
    extraArgs:
      "v": "4"

# patch for v1beta4 (future)
- |
  kind: ClusterConfiguration
  apiVersion: kubeadm.k8s.io/v1beta4
  apiServer:
    extraArgs:
      - name: "v"
        value: "4"

If you only need to target a particular release, you can use one version.

If you only need to target fields that did not change between kubeadm beta versions, you can use a versionless patch, which may be more convenient, but we cannot guarantee there will be no future kubeadm config breaking changes.

New Features

Assorted unspecified dependency updates

Images pre-built for this release:

v1.35.0: kindest/node:v1.35.0@sha256:452d707d4862f52530247495d180205e029056831160e22870e37e3f6c1ac31f
v1.34.3: kindest/node:v1.34.3@sha256:08497ee19eace7b4b5348db5c6a1591d7752b164530a36f855cb0f2bdcbadd48
v1.33.7: kindest/node:v1.33.7@sha256:d26ef333bdb2cbe9862a0f7c3803ecc7b4303d8cea8e814b481b09949d353040
v1.32.11: kindest/node:v1.32.11@sha256:5fc52d52a7b9574015299724bd68f183702956aa4a2116ae75a63cb574b35af8
v1.31.14: kindest/node:v1.31.14@sha256:6f86cf509dbb42767b6e79debc3f2c32e4ee01386f0489b3b2be24b0a55aac2b

NOTE: You must use the @sha256 digest to guarantee an image built for this release, until such a time as we switch to a different tagging scheme. Even then we will highly encourage digest pinning for security and reproducibility reasons.

Fixes

Detect additional edge case with ipv6 support on the host
Make development / release scripts GOTOOLCHAIN aware

Contributors

Committers for this release:

`v0.30.0`

This is small release containing patched dependencies and Kubernetes 1.34, as well as a bugfix for Kubernetes v1.33.0+ cluster reboots.

Breaking Changes

The default node image is now kindest/node:v1.34.0@sha256:7416a61b42b1662ca6ca89f02028ac133a309a2a30ba309614e8ec94d976dc5a

New Features

Updated to containerd 2.1.4

Images pre-built for this release:

v1.34.0: kindest/node:v1.34.0@sha256:7416a61b42b1662ca6ca89f02028ac133a309a2a30ba309614e8ec94d976dc5a
v1.33.4: kindest/node:v1.33.4@sha256:25a6018e48dfcaee478f4a59af81157a437f15e6e140bf103f85a2e7cd0cbbf2
v1.32.8: kindest/node:v1.32.8@sha256:abd489f042d2b644e2d033f5c2d900bc707798d075e8186cb65e3f1367a9d5a1
v1.31.12: kindest/node:v1.31.12@sha256:0f5cc49c5e73c0c2bb6e2df56e7df189240d83cf94edfa30946482eb08ec57d2

NOTE: You must use the @sha256 digest to guarantee an image built for this release, until such a time as we switch to a different tagging scheme. Even then we will highly encourage digest pinning for security and reproducibility reasons.

Fixes

Fix an issue with rebooting v1.33.0+ clusters #3941
Add priority class system-critical to kindnetd
Fix HA control-plane loadbalancer for podman #3962
Fix node-image builds with relative source paths

Contributors

Committers for this release:

Configuration

📅 Schedule: (in timezone Europe/Oslo)

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 this update again.

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

This PR has been generated by Mend Renovate CLI.

This PR contains the following updates: | Package | Update | Change | |---|---|---| | [kind](https://github.com/kubernetes-sigs/kind) | minor | `0.29.0` → `0.32.0` | --- ### Release Notes <details> <summary>kubernetes-sigs/kind (kind)</summary> ### [`v0.32.0`](https://github.com/kubernetes-sigs/kind/releases/tag/v0.32.0) This release contains critical dependency updates, bug fixes, and defaults to Kubernetes 1.36.1. ### Breaking Changes - **The default node image is now `kindest/node:v1.36.1@sha256:3489c7674813ba5d8b1a9977baea8a6e553784dab7b84759d1014dbd78f7ebd5`** - **New node images requiring upgrading kind to `kind load ...`**: Due to a containerd upgrade, you must upgrade `kind` to this release or newer to use `kind load ...` with the newly published node images. As always, we cannot gurantee full compatibility of node images between kind releases. You can use the digests from previous releases, upgrade kind, or build your own node-images. - **kubeadm v1beta4 config format is now used for Kubernetes 1.36.0+** If you are using versioned config patches, you must update to target v1beta4. Unversioned patches kind will attempt to convert as needed (more below in New Features). This change is required for Kubernetes 1.37+ which drops kubeadm v1beta3 config. - **Adoption of Envoy for Load Balancing in multi-control-plane node clusters:** HAProxy has been replaced by Envoy (`docker.io/envoyproxy/envoy:v1.36.2`) as the load balancer in multi-control-plane (HA) clusters. If you rely on custom HAProxy loadbalancer configurations or images, please note that Envoy is now used. - **cgroup v1 warning:** A warning is now printed if cgroup v1 is detected on the host. Kubernetes [has deprecated support for cgroup v1](https://github.com/kubernetes/enhancements/issues/5573), and at some point in the future KIND releases / node-images will also drop support for cgroup v1. ### New Features - **kubeadm v1beta4 configuration support:** KIND now uses the `v1beta4` config format for Kubernetes `v1.36.0+` while maintaining `v1beta3` for `v1.23.0` up to `v1.35.x`, and `v1beta2` for older versions. - **Custom Merging & Version-Awareness for Kubeadm Config Patches:** - KIND now automatically translates old-style map-based `extraArgs` / `kubeletExtraArgs` patches to the list-based `v1beta4` format when targeting `v1beta4` configs. - Config patches now append to `extraArgs` / `kubeletExtraArgs` / `certSANs` reliably. To overwrite or make other more precise patching, use json6902 patches. - **Support for containerd config v4 format:** Enabled support for containerd's config v4 format in `kind load` and snapshotter parsing, which is required for newer containerd versions. - **Building Node Images from CI Artifacts:** Added support to build node images from Kubernetes CI artifacts (resolving endpoints like `https://dl.k8s.io/ci/latest.txt` or CI build prefixes). - **Support for containerd version-aware containerd config patching:** Like kubeadmConfigPatches, containerd config patching is now aware of `version` and if specified in patches will only apply patches that match the containerd config being used. - Assorted dependency updates. Images pre-built for this release: - v1.36.1: `kindest/node:v1.36.1@sha256:3489c7674813ba5d8b1a9977baea8a6e553784dab7b84759d1014dbd78f7ebd5` - v1.35.5: `kindest/node:v1.35.5@sha256:ce977ae6d65918d0b58a5f8b5e940429c2ce42fa3a5619ec2bbc60b949c0ac95` - v1.34.8: `kindest/node:v1.34.8@sha256:02722c2dedddcfc00febf5d27fbeb9b7b2c14294c82109ff4a85d89ac9ba3256` - v1.33.12: `kindest/node:v1.33.12@sha256:3f5c8443c620245e4d355cfe09e96a91ead32ceaa569d3f1ca9edf0cb2fe2ff4` **NOTE**: You *must* use the `@sha256` digest to guarantee an image built for this release, until such a time as we switch to a different tagging scheme. Even then we will highly encourage digest pinning for security and reproducibility reasons. ### Fixes - Fix permission error when creating pods with `hostUsers: false` (Kubernetes 1.36+). - Handle registry ports correctly in image normalization logic (e.g., registry running on ports like `localhost:5000/...`). - Handle empty port mapping listen addresses correctly (defaults to wildcard address). - Skip `/dev/mapper` mount on rootless Docker. - Assorted documentation fixes and improvements. See also: - <https://kind.sigs.k8s.io/docs/user/quick-start/#creating-a-cluster> - <https://kind.sigs.k8s.io/docs/user/quick-start/#building-images> NOTE: These node images support amd64 and arm64, both of our supported platforms. **You must use the same platform as your host,** for more context see [#2718](https://github.com/kubernetes-sigs/kind/issues/2718) ### Contributors Committers for this release: - [@AnjaliMishra1st](https://github.com/AnjaliMishra1st) - [@aojea](https://github.com/aojea) - [@BenTheElder](https://github.com/BenTheElder) - [@dependabot](https://github.com/dependabot)\[bot] - [@dims](https://github.com/dims) - [@egypcio](https://github.com/egypcio) - [@george-angel](https://github.com/george-angel) - [@immanuwell](https://github.com/immanuwell) - [@k8s-ci-robot](https://github.com/k8s-ci-robot) - [@rjbrown57](https://github.com/rjbrown57) - [@shwetha-s-poojary](https://github.com/shwetha-s-poojary) - [@stmcginnis](https://github.com/stmcginnis) - [@tmchow](https://github.com/tmchow) - [@yesdeepakverma](https://github.com/yesdeepakverma) We'd also like to thank everyone who touched the codebase, filed issues, and helped the community! ### [`v0.31.0`](https://github.com/kubernetes-sigs/kind/releases/tag/v0.31.0) This release contains dependency updates and defaults to Kubernetes 1.35.0. Please take note of the breaking changes from Kubernetes 1.35, and how to prepare for **future** changes to move off of the deprecated kubeam v1beta3 in favor of v1beta4. We will include updated reminders for both again in subsequent releases. <h1 id="breaking-changes">Breaking Changes</h1> The default node image is now `kindest/node:v1.35.0@sha256:452d707d4862f52530247495d180205e029056831160e22870e37e3f6c1ac31f` <h2 id="kubernetes-cgroupv1">Kubernetes 1.35+ Cgroup v1</h2> Kubernetes [will be removing cgroup v1 support](https://kubernetes.io/blog/2025/12/17/kubernetes-v1-35-release/#removal-of-cgroup-v1-support), and therefore kind node images at those versions will also be dropping support. You can read more about this change in the Kubernetes release blog: <https://kubernetes.io/blog/2025/12/17/kubernetes-v1-35-release/#removal-of-cgroup-v1-support> If you must use kind on cgroup v1, we recommend using an older Kubernetes release for the immediate future, but we also strongly recommend migrating to cgroup v2. In the near future as Kubernetes support dwindles, KIND will also clean up cgroup v1 workarounds and drop support in future kind releases and images, regardless of Kubernetes version. Most stable linux distros should be on cgroupv2 out of the box. This is a reminder to use pinned images by digest, see the note below about images for this release. <h2 id="kubeadm-config">Kubeadm Config *Future* Breaking Change</h2> **WARNING**: Future kind releases will [adopt kubeadm v1beta4](https://github.com/kubernetes-sigs/kind/issues/3847) configuration, [kubeadm](https://github.com/kubernetes/kubeadm) v1beta4 has a breaking change to `extraArgs`: <https://kubernetes.io/blog/2024/08/23/kubernetes-1-31-kubeadm-v1beta4/>. If you use the `kubeadmConfigPatches` feature then you may need to prepare for this change. We recommend that you use versioned config patches that explicitly match the version required. KIND uses kubeadm v1beta3 for Kubernetes 1.23+, and will likely use v1beta4 for Kubernetes 1.36+ The exact version is TBD pending work to fix this but expected to be 1.36. It will definitely be an as-of-yet-unreleased Kubernetes version to avoid surprises, and it will not be on a patch-release boundary. KIND *may* still work with older Kubernetes versions at v1beta2, but we no longer test or actively support these as Kubernetes only supports 1.32+ currently: <https://kubernetes.io/releases/> You likely only need v1beta3 + v1beta4 patches, you can take your existing patches that work with v1beta3, explicitly set `apiVersion: kubeadm.k8s.io/v1beta3` in the patch at the top level, and make another copy for v1beta4. The v1beta4 patch will need to move `extraArgs` from a map to a list, for examples see: <https://kubernetes.io/docs/reference/config-api/kubeadm-config.v1beta4/> For a concrete example of kind config with kubeadm config patch targeting both v1beta3 and v1beta4, consider this simple kind config that sets verbosity of the apiserver logs: ```yaml kind: Cluster apiVersion: kind.x-k8s.io/v1alpha4 kubeadmConfigPatches: # patch for v1beta3 (1.23 ...) - | kind: ClusterConfiguration apiVersion: kubeadm.k8s.io/v1beta3 apiServer: extraArgs: "v": "4" # patch for v1beta4 (future) - | kind: ClusterConfiguration apiVersion: kubeadm.k8s.io/v1beta4 apiServer: extraArgs: - name: "v" value: "4" ``` If you only need to target a particular release, you can use one version. If you only need to target fields that did not change between kubeadm beta versions, you can use a versionless patch, which may be more convenient, but we cannot guarantee there will be no future kubeadm config breaking changes. <h1 id="new-features">New Features</h1> - Assorted unspecified dependency updates Images pre-built for this release: - v1.35.0: `kindest/node:v1.35.0@sha256:452d707d4862f52530247495d180205e029056831160e22870e37e3f6c1ac31f` - v1.34.3: `kindest/node:v1.34.3@sha256:08497ee19eace7b4b5348db5c6a1591d7752b164530a36f855cb0f2bdcbadd48` - v1.33.7: `kindest/node:v1.33.7@sha256:d26ef333bdb2cbe9862a0f7c3803ecc7b4303d8cea8e814b481b09949d353040` - v1.32.11: `kindest/node:v1.32.11@sha256:5fc52d52a7b9574015299724bd68f183702956aa4a2116ae75a63cb574b35af8` - v1.31.14: `kindest/node:v1.31.14@sha256:6f86cf509dbb42767b6e79debc3f2c32e4ee01386f0489b3b2be24b0a55aac2b` **NOTE**: You *must* use the `@sha256` digest to guarantee an image built for this release, until such a time as we switch to a different tagging scheme. Even then we will highly encourage digest pinning for security and reproducibility reasons. See also: - <https://kind.sigs.k8s.io/docs/user/quick-start/#creating-a-cluster> - <https://kind.sigs.k8s.io/docs/user/quick-start/#building-images> NOTE: These node images support amd64 and arm64, both of our supported platforms. **You must use the same platform as your host,** for more context see [#2718](https://github.com/kubernetes-sigs/kind/issues/2718) <h1 id="fixes">Fixes</h1> - Detect additional edge case with ipv6 support on the host - Make development / release scripts GOTOOLCHAIN aware <h1 id="contributors">Contributors</h1> Committers for this release: - [@AkihiroSuda](https://github.com/AkihiroSuda) - [@adambkaplan](https://github.com/adambkaplan) - [@afbjorklund](https://github.com/afbjorklund) - [@aoxn](https://github.com/aoxn) - [@BenTheElder](https://github.com/BenTheElder) - [@dependabot](https://github.com/dependabot)\[bot] - [@k8s-ci-robot](https://github.com/k8s-ci-robot) - [@kalexmills](https://github.com/kalexmills) - [@kishen-v](https://github.com/kishen-v) - [@mikejoh](https://github.com/mikejoh) - [@rayowang](https://github.com/rayowang) - [@shahar1](https://github.com/shahar1) - [@stmcginnis](https://github.com/stmcginnis) ### [`v0.30.0`](https://github.com/kubernetes-sigs/kind/releases/tag/v0.30.0) This is small release containing patched dependencies and Kubernetes 1.34, as well as a bugfix for Kubernetes v1.33.0+ cluster reboots. <h1 id="breaking-changes">Breaking Changes</h1> The default node image is now `kindest/node:v1.34.0@sha256:7416a61b42b1662ca6ca89f02028ac133a309a2a30ba309614e8ec94d976dc5a` <h1 id="new-features">New Features</h1> - Updated to containerd 2.1.4 Images pre-built for this release: - v1.34.0: `kindest/node:v1.34.0@sha256:7416a61b42b1662ca6ca89f02028ac133a309a2a30ba309614e8ec94d976dc5a` - v1.33.4: `kindest/node:v1.33.4@sha256:25a6018e48dfcaee478f4a59af81157a437f15e6e140bf103f85a2e7cd0cbbf2` - v1.32.8: `kindest/node:v1.32.8@sha256:abd489f042d2b644e2d033f5c2d900bc707798d075e8186cb65e3f1367a9d5a1` - v1.31.12: `kindest/node:v1.31.12@sha256:0f5cc49c5e73c0c2bb6e2df56e7df189240d83cf94edfa30946482eb08ec57d2` **NOTE**: You *must* use the `@sha256` digest to guarantee an image built for this release, until such a time as we switch to a different tagging scheme. Even then we will highly encourage digest pinning for security and reproducibility reasons. See also: - <https://kind.sigs.k8s.io/docs/user/quick-start/#creating-a-cluster> - <https://kind.sigs.k8s.io/docs/user/quick-start/#building-images> NOTE: These node images support amd64 and arm64, both of our supported platforms. **You must use the same platform as your host,** for more context see [#2718](https://github.com/kubernetes-sigs/kind/issues/2718) <h1 id="fixes">Fixes</h1> - Fix an issue with rebooting v1.33.0+ clusters [#3941](https://github.com/kubernetes-sigs/kind/issues/3941) - Add priority class system-critical to kindnetd - Fix HA control-plane loadbalancer for podman [#3962](https://github.com/kubernetes-sigs/kind/pull/3962) - Fix node-image builds with relative source paths <h1 id="contributors">Contributors</h1> Committers for this release: - [@BenTheElder](https://github.com/BenTheElder) - [@dims](https://github.com/dims) - [@k8s-ci-robot](https://github.com/k8s-ci-robot) - [@oduludo](https://github.com/oduludo) - [@stmcginnis](https://github.com/stmcginnis) - [@tchap](https://github.com/tchap) - [@tom1299](https://github.com/tom1299) </details> --- ### Configuration 📅 **Schedule**: (in timezone Europe/Oslo) - 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 this update again. --- - [ ] If you want to rebase/retry this PR, check this box --- This PR has been generated by [Mend Renovate CLI](https://github.com/renovatebot/renovate).

gitea_admin added 1 commit 2026-09-27 00:09:00 +00:00

chore(deps): update dependency kind to v0.32.0

renovate/stability-days Updates have met minimum release age requirement

Details

/ test (pull_request) Successful in 24s

Details

a7861f26b7

danijel.simeunovic was assigned by gitea_admin

2026-09-27 00:09:05 +00:00

gitea_admin requested review from danijel.simeunovic 2026-09-27 00:09:06 +00:00

danijel.simeunovic approved these changes 2026-09-27 22:14:05 +00:00

gitea_admin changed title from ~~chore(deps): update dependency kind to v0.32.0~~ to chore(deps): update dependency kind to v0.32.0 - autoclosed

2026-09-28 00:19:06 +00:00

gitea_admin closed this pull request

2026-09-28 00:19:06 +00:00

Pull request closed

This pull request cannot be reopened because the branch was deleted.

Sign in to join this conversation.

2 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Forte/launchpad#36