x/tools/gopls: release gopls@v0.16.0-pre.1 prior to 1.23rc1

[findleyr]

This issue exists to block the release of go1.23rc1 on the existence of a gopls@v0.16.0-pre.1 release.

gopls@master has support for 1.23 features that does not yet exist in gopls@latest. Notably:

• Support for range-over-func (including SSA)
• Support for gotypesalias=1
• Support for the new API of runtime.SetCrashOutput (currently, gopls@latest doesn't built with go1.23 due to an API change)
• (soon) support for godebug directives in go.mod and go.work files

Ideally, we'd like to release gopls@v0.16.0 prior to go1.23rc1, so that gopls users can experiment with the new language features. At the very least, we should have a gopls prerelease with this support before the Go release candidate.

See the gopls/v0.16.0 milestone for the current status of this release.

CC @dmitshur @joedian

[adonovan]

I notice that x/tools/internal/stdlib doesn't include go1.23 symbols yet, because the various api/next/*.txt files haven't yet been consolidated into go1.23.txt. What causes that to happen? (Paging @mknyszek author of https://go.dev/cl/544555.)

[dmitshur]

The timing of api files being merged isn't exactly the same as in past releases because they're also involved in the test for improved release notes (#64169). I'm working on that for this cycle, so feel free to ping me instead of Michael.

The task that updates x/tools/internal/stdlib nominally happens during the go1.N.0 (final) release, not RC 1:

https://cs.opensource.google/go/x/build/+/master:internal/relui/workflows.go;l=487-491;drc=ef977b72d670c8f407e16e2b411ce7b95dd80474

[adonovan]

Wait, you already have a release automation task to update x/tools/internal/stdlib? Wow, you are on it!

[findleyr]

-pre.1 is released, so this is done.

Given the updated RC timing, we hope to actually release v0.16.0 prior to the RC, but this need not block the RC.