You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
CI: canary failing after the release of go1.27rc1 #4979
level=warning msg="[runner] Can't run linter goanalysis_metalinter: inspect: failed to load package context: could not load export data: internal error in importing \"context\" (cannot decode \"context\", export data version 4 is greater than maximum supported version 2); please report an issue"
level=error msg="Running error: can't run linter goanalysis_metalinter\ninspect: failed to load package context: could not load export data: internal error in importing \"context\" (cannot decode \"context\", export data version 4 is greater than maximum supported version 2); please report an issue"
make[1]: *** [Makefile:142: lint-go] Error 3
make[1]: Leaving directory '/home/runner/work/nerdctl/nerdctl'
make: *** [Makefile:148: lint-go-all] Error 2
Updating golangci-lint from v2.4.0 to latest on my local environment resolves the following error seen in CI.
level=warning msg="[runner] Can't run linter goanalysis_metalinter: inspect: failed to load package context: could not load export data: internal error in importing "context" (cannot decode "context", export data version 4 is greater than maximum supported version 2); please report an issue"
level=error msg="Running error: can't run linter goanalysis_metalinter\ninspect: failed to load package context: could not load export data: internal error in importing "context" (cannot decode "context", export data version 4 is greater than maximum supported version 2); please report an issue"
make[1]: *** [Makefile:142: lint-go] Error 3
However, a different error then occurs. I reproduced it on Lima:
Activity
AkihiroSuda commentedon Jun 19, 2026
Workaround was applied to skip the canary:
haytok commentedon Jun 20, 2026
Updating
golangci-lintfromv2.4.0tolateston my local environment resolves the following error seen in CI.However, a different error then occurs. I reproduced it on Lima:
Details
This error appears to be related to the following issues: