Hi @k8s-infra-cherrypick-robot. Thanks for your PR.

I'm waiting for a containerd member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Looks like golangci-lint config is borked in this branch 😢

cc @austinvazquez in case you're near a computer to have a peek

Error: Failed to run: Error: Command failed: /home/runner/golangci-lint-1.60.3-linux-arm64/golangci-lint config verify
jsonschema: "run" does not validate with "/properties/run/additionalProperties": additionalProperties 'skip-dirs' not allowed
Failed executing command with error: the configuration contains invalid elements
, Error: Command failed: /home/runner/golangci-lint-1.60.3-linux-arm64/golangci-lint config verify
jsonschema: "run" does not validate with "/properties/run/additionalProperties": additionalProperties 'skip-dirs' not allowed
Failed executing command with error: the configuration contains invalid elements

Maybe it needs an updated version, as it looks to be quite behind

That's an odd error. My instinct is this is related to a golang-lint-action release over the past few days because release/1.7 and release/1.6 are using floating tag syntax in CI. i.e.

Hmm, possibly? I was looking at the version of the linter itself, but perhaps it's the action yes;

Made #11400 which should fix this on 1.7 branch. The issuse is because the latest golangci-lint action version (v6.5.0) enabled json schema check, which exposed a deprecated field that has been removed in the golangci-lint version (v1.60.3) we use. cc @thaJeztah @austinvazquez

The 1.6 branch doesn't have this issue because we're using a pretty old golangci-lint version which hasn't removed this deprecated field.

@thaJeztah Rebasing this on latest release/1.7/HEAD should fix those CI lint errors. If we can't force the bot to do it, maybe we should just close this and file a new one with the same cherry-picked commit.

Thanks for bringing this in; sorry, had a busy day 🙈