@cherrymui requested issue #68088 to be considered for backport to the next 1.22 minor release.

@gopherbot please backport this to Go 1.22. Thanks.

Reason is similar to the freeze exception above. Xcode 16 will probably be released while Go 1.22 is still in support.

Comment From: cherrymui

Go 1.21 will be out of support soon, certainly before Xcode 16 is released. So I don't think we need to do Go 1.21.

Comment From: gabyhelp

Similar Issues

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)

Comment From: joedian

@cherrymui agreed to approve , however please create backport for 1.21 as well.

Comment From: cherrymui

however please create backport for 1.21 as well.

As commented above https://github.com/golang/go/issues/68198#issuecomment-2191912515 I don't think we need to backport to Go 1.21. Could you explain why that is necessary? Thanks.

Comment From: dmitshur

Our default policy decision is to support all supported versions of Go equally. See accepted proposal 34536. Since this problem affects both Go 1.22 and 1.21, it seemed that 1.21 should get the fix too.

I was going to suggest that if backporting to Go 1.21 creates unreasonable overhead, it's likely fine to wait a bit while Xcode 16 is still in beta, and revisit this after Go 1.23.0 is out, but I understand you were making the same point in https://github.com/golang/go/issues/68198#issuecomment-2191912515 in that the problem isn't there now, but in the future, and by then 1.23 and 1.22 will be supported. So I think it is indeed okay to move forward with 1.22 only from that perspective. Thanks.

Comment From: gopherbot

Change https://go.dev/cl/596455 mentions this issue: [release-branch.go1.22] cmd/link: don't let dsymutil delete our temp directory

Comment From: gopherbot

Closed by merging 4e548f2c8e489a408033c8aab336077b16bc8cf7 to release-branch.go1.22.