🌱 Use go version without the patch number in go.mod files #696
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
Looks like we need to avoid using go version with patch number included in the go.mod files
Similar issue was reported in siderolabs/conform#251 and suggestion was to remove patch number from the version.
Which issue(s) this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)
format, will close the issue(s) when PR gets merged):Fixes #
Unfortunately, when running locally the same target (
make release-manifests
) it passes and there is no way to test it other then merging and watching the job in https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/post-cluster-api-operator-push-images