Fix updating of go.mod
entries for components
#1103
Merged
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.
We noticed that some of our components had not received
go.mod
updateswhile they did receive updates for the versions declared in the YAML
manifests.
Was able to trace this back to a behavior change in Go since
1.16.x
,resulting in it no longer making automated changes to
go.mod
andgo.sum
1. This is an issue for our updater script as it relieson
go list -m all
, which now after the firstgo mod edit
returns:To work around the issue without having to repeatedly call
go mod tidy
,I have opted to simply
grep
on the contents ofgo.mod
as aworkaround.