k6: pin go version to 1.23

[mstoykov]

Fixing grafana/k6#2699

• Have you followed the guidelines for contributing?
• Have you ensured that your commits follow the commit style guide?
• Have you checked that there aren't other open pull requests for the same formula update/change?
• Have you built your formula locally with HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
• Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
• Does your build pass brew audit --strict <formula> (after doing HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

---

[github-actions]

Thanks for contributing to Homebrew! 🎉 It looks like you're having trouble with a CI failure. See our contribution guide for help. You may be most interested in the section on dealing with CI failures. You can find the CI logs in the Checks tab of your pull request.

[stefanb]

FYI, initial builds and tests with Go 1.24 in the

• go 1.24rc2, [email protected] 1.23.5 (new formula) #201070

found no issues with k6.

[chenrui333]

* Dependency '[email protected]' is an alias; use the canonical name 'go'.

this might need to wait after #201070

[mstoykov]

Can we not pin the latest version we need to pin to an old one if we want ?

[mstoykov]

@stefanb I am aware it will compile or that the test will pass - we have been running our tests with gotip for years. Even before the issue linked.

The problem is that we weren't testing for this particular case and likely won't for the next case that breaks something.

We just want that instead of us building with whatever is the latest go version we bump it when we bump it within k6.
The same way I would not make a docker container that just gets the latest .. ubuntu and then install something and hope that between versions of ubuntu nothing will change. I would want to stick to the version of go that we are using to building within the team and then bump on our time.

Currently, it seems that pinning to [email protected] is a lint error as it is alias to go and that apparently is a problem.
So:

1. we can set it to 1.23 and ignore the lint somehow
2. actually this shouldn't be a lint error as otherwise I don't know why the alias exist if using it is a lint error 🤔
3. we can pin to go1.22 which means that we will have similar problem - our official builds will be with a different version from brew
4. I guess brew can start using the prebuild binary instead of building it - I think there was a policy against that though
5. We can just ignore this and close this PR

@stefanb , @chenrui333 I don't know if you can help with any of this or point me to documentation about any of the approaches and reasons for the policies and linters.