Go Ports Can Now Declare What Version of Go They Need

[Herby G]

Much appreciated. Going forward, we'll keep annotating Go ports with
`go.toolchain_min` until the right thing is happening for all Go project
ports in the MacPorts catalog.

Secondly, I need to correct one point from my initial announcement:

In point 3, I stated that this can't be used with projects which use
`go.vendors`.
That's not entirely correct. Since `go.vendors` is generated off of a
project's
`go.mod`, `go.toolchain_min` can still be specified. It will still gate a
project
from attempting to build on a system where the Go toolchain version it
requires is not available.


On Tue, Aug 4, 2026 at 8:41 AM Joshua Root <jmr at macports.org> wrote:

> On 4/8/2026 04:54, Herby G wrote:
> > The `go` port is now a thin wrapper that provides the newest Go compiler
> > release each system can actually run:
> >
> >      macOS 10.7 - 10.12    -> Go 1.17
> >      macOS 10.13 - 11      -> Go 1.24
> >      macOS 12 and later    -> Go 1.26
> >
> > The versioned toolchains are installed side by side as go-1.NN, and a new
> > go_toolchain PortGroup owns the mapping. Background and reasoning are in
> > https://trac.macports.org/ticket/73086 <https://trac.macports.org/
> > ticket/73086> -- this note is just what maintainers
> > need to do.
> >
> > This mechanism prevents a Go port from attempting to build on an
> unsupported
> > version of macOS where it cannot be built or run. In this way, we
> > increase Buildbot
> > efficiency and improve the user experience for Go port users.
> Thank you. This looks like a great improvement.
>
> - Josh
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.macports.org/pipermail/macports-dev/attachments/20260808/f4f91314/attachment.htm>