go 1.20.1#122082
Conversation
c900656 to
639a79e
Compare
|
Similar to #107165, have bumped the revision |
72b6be3 to
ea55d35
Compare
ea55d35 to
839e958
Compare
|
We might just want to cherry-pick |
I think it might be better to put in this same PR, some formulae won't work go@1.20 |
|
We usually ship the older version in a separate PR after the PR for the newer one is merged. |
|
@carlocab There are a couple of projects which haven't been responsive to the compatibility issues referencing Homebrew. If they don't update quickly, we'll probably need the older version to merge without breaking the tests |
|
If they're not responsive to being compatible with supported Go versions they should be moved to any older Go version and deprecated. The fact that we're building their project should have no influence on this. |
Errors from macOS 13 on Intel:Nothing additional for macOS 13/12/11 on Apple Silicon Nothing additional for macOS 12 on Intel Additional errors for macOS 11 on Intel:Additional errors on Linux:The full list of actual formulae:Do we basically just want to update all of these to depend on go@1.19? |
We should check what broke and fix it. If upstream is deprecated we can use an older Go version. |
|
#122203 staticcheck updated |
8289d84 to
6f65b25
Compare
|
Any help needed here? Big block for our CI and willing to lend a hand if needed. Thanks to all for the OSS work |
Just waiting for the CI now before we review the failures again, hopefully nothing too big anymore. It takes ~24 hours for a full CI run across all platforms. |
|
@chenrui333 any ideas on the |
That error comes when GOROOT is for a different go version than the go binary that is being run. The formula picks up the wrong go binary. I think you need to prepend I think this may be a problem in the other formulas too, maybe |
|
I would like to thank developers for their work. I use this package for long time and I see similar troubles every major Go release. What is nice to see on next release:
Thanks! |
Make sure all projects that brew packages are prepared for future Go versions by helping them set up CI that tests with nightlies. Otherwise brew will be the first one to test their software with a new Go release.
Make sure all projects that brew packages are prepared for future Go versions by notifying them when a new Go release is out. Otherwise brew will be the first one to test their software with a new Go release.
It exists, but not in brew. See the comments here to see how. |
|
I've filed a separate proposal to try to deal with the mismatch of user expectations around build tool releases. Please comment there instead of here unless you are talking about how to fix the broken Go formulae: Homebrew/brew#14749. |
|
I guess this "otherwise" is happening now :-)
I know, I can read pretty well. @carlmjohnson has provided more informative explanation above. |
p-linnane
left a comment
There was a problem hiding this comment.
This looks good. We will open separate PR's to deal with the 3 remaining issues. Thank you to everyone for your patience and help to get this merged.
|
Please open an issue or post in discussions if you are having problems. This PR has run it's course. |


Created with
brew bump-formula-pr.resourceblocks may require updates.