Upgrading the go version in build files #474
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Signed-off-by: Adarsh kumar <[email protected]>
Jonsy13
reviewed
Jul 4, 2023
|
go.mod also needs to be updated! |
Signed-off-by: Adarsh kumar <[email protected]>
uditgaurav
approved these changes
Jul 18, 2023
Jonsy13
approved these changes
Jul 18, 2023
AlvaroGG0
pushed a commit
to AlvaroGG0/chaos-operator
that referenced
this pull request
Apr 19, 2024
* updating the go version in build files Signed-off-by: Adarsh kumar <[email protected]> * Updating go version Signed-off-by: Adarsh kumar <[email protected]> --------- Signed-off-by: Adarsh kumar <[email protected]> Signed-off-by: Alvaro Gutierrez <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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:
Upgrading the go version in build files to 1.20 to fix the vulnerabilities
Which issue this PR fixes (optional, in
fixes #<issue number>(, fixes #<issue_number>, ...)format, will close that issue when PR gets merged): fixes #Special notes for your reviewer:
Checklist:
documentationtagbreaking-changestagrequires-upgradetag