Conversation
|
As usual we are waiting for 1.26.1 to be released. It seems that this is happenign on the 3rd of March so we can probably get this reviewed before that. 1.26.1 while a security update (usually) includes other bugfixes to general not security related usage |
| o.wg.Add(1) | ||
| go func() { | ||
| defer o.wg.Done() | ||
| o.wg.Go(func() { |
There was a problem hiding this comment.
Can we move this change in a separated pull request so we can just merge it now and start testing it, please?
There was a problem hiding this comment.
No because the linter is failing wihtout htis - this was created with golangci-lint run --fix ./...
There was a problem hiding this comment.
Does it fail because the linter requires 1.26.x? Because if we merge wg.Go changes first then I don't get why it should fail.
There was a problem hiding this comment.
No it fails, because when we now have the minimum at 1.25 we can use wg.Go - so modernize wants us to
Co-authored-by: Joan López de la Franca Beltran <5459617+joanlopez@users.noreply.github.com>
- The k6-builder Docker image runs Go 1.24.4 with `GOTOOLCHAIN=local` - k6 `master` now requires `go >= 1.25.0` (since grafana/k6#5702) - All non-cached builds have been failing with 500 for 4 days, affecting multiple customers - Related escalation: grafana/support-escalations#21169
What?
Update to using 1.26 as the default, and 1.25 as the minimum version k6 supports. Also fix lint issues due to minimum 1.25 gives us some new tools.
Why?
Updating go version is required as well as lint fixes.
Checklist
make check) and all pass.Checklist: Documentation (only for k6 maintainers and if relevant)
Please do not merge this PR until the following items are filled out.
Related PR(s)/Issue(s)