x/tools/internal/imports: update stdlib index after every major Go release #38706
Comments
Change https://golang.org/cl/246581 mentions this issue: |
$ go run mkstdlib.go Updates golang/go#38706. Change-Id: I9d1bba54c4f9a0369b1d088c00a2f0c3e4409806 Reviewed-on: https://go-review.googlesource.com/c/tools/+/246581 Run-TryBot: Akhil Indurti <aindurti@gmail.com> Run-TryBot: Heschi Kreinick <heschi@google.com> TryBot-Result: Gobot Gobot <gobot@golang.org> Reviewed-by: Heschi Kreinick <heschi@google.com>
@golang/release might have something to say about this. |
Change https://golang.org/cl/293839 mentions this issue: |
As a first step, let's make this a recurring early-in-cycle release-blocking issue, similar to #40705 and #36905, so that this task isn't missed. (If it's viable to automate this task so it doesn't need to be done by hand every 6 months, please file a new issue for doing that work.) I'll place it in Go 1.17 milestone now, and when CL 293839 is submitted, it can be moved to Go 1.18. |
Strictly speaking it would probably make it sense to do it shortly before the release, once the API has stabilized. But right after is fine too. |
@heschik Yep, that makes sense. The reason I've used this early-in-cycle path for now is the same reason I closed #27155 (comment): we currently don't have a good system for tracking issues that aren't actionable until very late in a dev cycle. When we do, we can improve this task so it happens late in cycle instead. |
$ go run mkstdlib.go Updates golang/go#38706. Change-Id: I9d5bce3083d2a57eea2ea89c6a99a410ed169f05 Reviewed-on: https://go-review.googlesource.com/c/tools/+/293839 Run-TryBot: Akhil Indurti <aindurti@gmail.com> Run-TryBot: Heschi Kreinick <heschi@google.com> Reviewed-by: Heschi Kreinick <heschi@google.com> Trust: Heschi Kreinick <heschi@google.com> Trust: Hyang-Ah Hana Kim <hyangah@gmail.com> gopls-CI: kokoro <noreply+kokoro@google.com> TryBot-Result: Go Bot <gobot@golang.org>
API changes should automatically be detected by x/tools/internal/imports after each major release. After 1.14, they were manually updated as per #38464. This should be part of the release process (maybe x/build/cmd/releasebot?).
The text was updated successfully, but these errors were encountered: