Re: Updating golang-gopkg-yaml.v3 to v3.0.5

[Arthur Diniz]

Hi,




I'm in the middle of bumping the Kubernetes-related packages to


That explains errors like:



and the kube-openapi document_v3.go yaml.v3 type mismatch, these are
transitional and resolve as the dependency chain gets updated together.

Progress so far, already uploaded:

- golang-k8s-sigs-structured-merge-diff
- golang-k8s-klog
- golang-k8s-sigs-yaml
- golang-k8s-sigs-json
- golang-github-google-gnostic-models
- golang-k8s-kube-openapi

Next in the queue to review and upload (in dependency order):

1. golang-k8s-apimachinery -- OK, MR ready
2. golang-k8s-api -- in review
3. golang-k8s-client-go -- in review
4. golang-k8s-cli-runtime -- in review








Thanks,
Arthur


On 11/09/2026 15:49, Nicolas Peugnet wrote:

I wanted to flag that several of the failures you listed, especially the ones going through kube-openapi and structured-merge-diff, line up with work I'm currently doing. bring them up to the 0.36.4 line, which involves the structured-merge-diff v6 switch and the corresponding kube-openapi/gnostic-models updates. cannot use typeSchema.Types (variable of type []"sigs.k8s.io/structured-merge-diff/v6/schema".TypeDef) as []"sigs.k8s.io/structured-merge-diff/schema".TypeDef Until this whole chain lands, expect reverse-dependency autopkgtests to keep failing (client-go, component-base, cli-runtime, kubernetes, cosign, etc. from your list are all downstream of this). Those should clear once the packages above are all in. While I'm at it, I'm also fixing the packages that currently FTBFS with Go 1.27 and closing the bugs filed against them (for example the encoding/json/v2 default-on change in 1.27 breaks a few test suites). So I'd treat the kube-openapi / structured-merge-diff / apimachinery-related failures in your list as expected-in-transition rather than new regressions.

I noticed that the whole Go ecosystem is being marked as AUTORM due to the FTBS of golang-github-rogpeppe-go-internal (#1146612), which is an indirect dependency of testify, through golang-gopkg-yaml.v3.

-----------------------------

[...]
2026/09/11 14:03:20 Completed building 1063 packages with 8 workers
2026/09/11 14:03:20 144 packages failed the first pass;
-----------------------------





-----------------------------
# k8s.io/kube-openapi/pkg/util/proto

-----------------------------

I also noticed that the v3.0.5 of golang-gopkg-yaml.v3 dropped this dependency, so I started updating it locally to this version. I'm currently running ratt with this command: $ nice ratt -dist unstable -parallel -jobs=8 -skip_ftbfs ~/debian/ golang-gopkg-yaml.v3_3.0.5-1_amd64.changes The first pass managed to build most of the packages but some of them failed due to "No space left on device" errors so I'm currently re- running them, and most of them seems to pass in the end. A few of them seem to be really broken with this update, mainly through kube-openapi: src/k8s.io/kube-openapi/pkg/util/proto/document_v3.go:291:31: cannot use s.GetDefault().ToRawInfo() (value of type *"go.yaml.in/yaml/v3".Node) as *"gopkg.in/yaml.v3".Node value in argument to parseV3Interface I will proceed to upload this new version soon as I think it will be better than the current situation. P.S. the second pass left only 56 packages failing but I still have missing space errors, I'm doing a last pass with parallelism disabled as I suspect this is the source of this issue.

OpenPGP_signature.asc
Description: OpenPGP digital signature