Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Hi @Sunnatillo. Thanks for your PR.

I'm waiting for a cri-o 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.

/ok-to-test

I am bit lost to use nix packages which container go v1.24.6. I would really appreciate if someone points how to fix following error:
go: go.mod requires go >= 1.24.6 (running go 1.24.5; GOTOOLCHAIN=local)

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 67.03%. Comparing base (d79c6c6) to head (43efb3a).
⚠️ Report is 8 commits behind head on main.

@@            Coverage Diff             @@
##             main    #9429      +/-   ##
==========================================
- Coverage   67.15%   67.03%   -0.13%     
==========================================
  Files         202      202              
  Lines       27900    27900              
==========================================
- Hits        18737    18703      -34     
- Misses       7594     7625      +31     
- Partials     1569     1572       +3     

@Sunnatillo It might be fixed by this PR #9434 or we might have to wait for the nix upstream to have the go version

/retest

@Sunnatillo It might be fixed by this PR #9434 or we might have to wait for the nix upstream to have the go version

Will the changes related to uplift of nixpkgs be backported to release branches, specifically release 1.33?
AFAIU nixpkgs is used to build artifacts for releases as well. Will next patch release of 1.33 build against latest nixpkgs config?

@Sunnatillo I don't think so. We need to backport the nixpkg too.

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: Sunnatillo

The full list of commands accepted by this bot can be found here.

it went in as a part of #9437

@Sunnatillo I don't think so. We need to backport the nixpkg too.

Is it ok if I open PR nixpkgs uplift for release-1.33 branch?