Open thardeck opened 5 months ago
@thardeck thanks for creating this issue.
These might be slightly different issues from an initial check.
On the first PR, it seems that it failed to correctly update the pseudo version as the resulting version is not correctly formatted:
sigs.k8s.io/kustomize/api 2e6171a9ea9a
sigs.k8s.io/kustomize/kyaml 2e6171a9ea9a
On the second, the issue was that the k8s.io/apiserver
was not bumped, and was kept at v0.29.2
. This should be done automatically as part of goModTidy. :thinking:
Many thanks for looking into it so quickly.
These might be slightly different issues from an initial check.
Should I create a different issue for the second one or leave it like this?
@thardeck thanks for creating this issue.
These might be slightly different issues from an initial check.
On the first PR, it seems that it failed to correctly update the pseudo version as the resulting version is not correctly formatted:
sigs.k8s.io/kustomize/api 2e6171a9ea9a sigs.k8s.io/kustomize/kyaml 2e6171a9ea9a
On the second, the issue was that the
k8s.io/apiserver
was not bumped, and was kept atv0.29.2
. This should be done automatically as part of goModTidy. 🤔
Running go mod tidy
should not change anything because our CI runs it and complains if there are any changes different from the pr.
Happy to leave as is. I think the second part of this issue may be tackled under https://github.com/rancher/renovate-config/issues/271, as I suspect they may have the same root cause. If not, we can create another issue at a later stage.
On the second, the issue was that the
k8s.io/apiserver
was not bumped, and was kept atv0.29.2
. This should be done automatically as part of goModTidy. 🤔
As expected I manually had to bump the k8s libraries to get the tests green: https://github.com/rancher/fleet/pull/2362/commits/d9ca814a01532226fc9e2d05bedadaffa4a064d7
It can not be done by just using go mod tidy
.
Renovate is unable to bump k8s libraries and does even realize that itself but still creates the pr. It reports:
This is the according pr: https://github.com/rancher/fleet/pull/2328
A similar issue is that renovate bumps k8s.io/kubernetes to v1.29.4 as security fix but does not bump the other k8s libraries which most likely is the reason for failing CI tests. Our unit tests report the following failures:
This is the according pr: https://github.com/rancher/fleet/pull/2362
The solution would most likely be when for example kubernetes is bumped to
1.29.4
, that all other k8s libraries are also bumped to0.29.4
to keep them in sync.I have not manually tested it in this case, but this is what I do when I bump these libraries on my own.