You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the brew recipe just builds k6 with the latest go in brew.
We in generally do not update the go version exactly after it comes out as it usually has performance changes and sometimes even small brekaing changes for us(usually in tests).
In the past we also had had a couple of cases of changes in having significant changes on how k6 operates so it's not always just "bump the version" kind of change.
Every other official package has the version pinned except brew which makes little to no senses and makes thigns such as #2474 (comment) harder to diagnose for users.
While we can't do anything about every non official package we can at least make it work for the ones we control.
The text was updated successfully, but these errors were encountered:
👍 , but I am not sure something like that will be accepted or if it's even possible. Generally, if they can, I think package maintainers try to use only a single compiler version for all packages with the same language in their repository 🤔
Currently, the brew recipe just builds k6 with the latest go in brew.
We in generally do not update the go version exactly after it comes out as it usually has performance changes and sometimes even small brekaing changes for us(usually in tests).
In the past we also had had a couple of cases of changes in having significant changes on how k6 operates so it's not always just "bump the version" kind of change.
Every other official package has the version pinned except brew which makes little to no senses and makes thigns such as #2474 (comment) harder to diagnose for users.
While we can't do anything about every non official package we can at least make it work for the ones we control.
The text was updated successfully, but these errors were encountered: