fix: lock go tool versions to reduce flakiness #580
Merged
Conversation
This file contains hidden or 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
skipi
requested review from
DamjanBecirovic,
VeljkoMaksimovic,
forestileao,
hamir-suspect and
lucaspin
as code owners
skipi
force-pushed
the
mk/lock-go-tool-versions
branch
4 times, most recently
from
227b547 to
c34babc
Compare
hamir-suspect
approved these changes
Sep 17, 2025
DamjanBecirovic
approved these changes
Sep 17, 2025
skipi
force-pushed
the
mk/lock-go-tool-versions
branch
from
c34babc to
ab426f1
Compare
lucaspin
approved these changes
Sep 18, 2025
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.
📝 Description
Due to recent go tool updates, we're getting red builds. To alleviate the issue, we're locking tool versions instead of using
latestones.✅ Checklist