> that means the intent of getting this fixed in go1.21.1 is recorded only in my head
It's okay to create the backport issue as soon as you think it should be considered for backport, before the iss…
@adonovan Note that manually placing an issue in a Go minor release milestone can lead to it being missed in weekly backport review and in [minor release note](https://go.dev/doc/devel/release#go1.25…
Now that the x/build module requires Go 1.25.0, it's viable to always
use CrossOriginProtection from the standard library instead of a copy
of it.
For golang/go#75899.
Thanks.
Since this line is a continuation of the previous one, consider indenting it to make that more visible. See line 109 for example.
Is the indentation change here intended?
Thanks. This was intended for a one-off workflow run for the Go 1.26 release cycle. That's done now and it successfully created go-directive-only [x/ repo CLs](https://go-review.googlesource.com/q/ow…
This is intended to make it possible to re-generate the
"all: upgrade go directive to at least 1.25.0 [generated]" CLs
for the Go 1.26 cycle with 'go fix ./...' not included.
The 'go fix ./...' invocation was included in the initial implementation
of the go directive maintenance workflow with the following rationale,
copied from https://go.dev/design/69095-x-repo-continuo…
Closing because this is on release-branch.go1.24 and probably not needed now that Go 1.26.0 is out. Feel free to reopen if it's still useful for something.
With the release of [Go 1.26.0](https://go.dev/doc/go1.26#introduction), the two latest supported major Go releases are 1.26 and 1.25 per the [Go release policy](https://go.dev/doc/devel/release#poli…
With the release of [Go 1.26.0](https://go.dev/doc/go1.26#introduction), the two latest supported major Go releases are 1.26 and 1.25 per the [Go release policy](https://go.dev/doc/devel/release#poli…
With the release of Go 1.26.0, the two latest supported major Go releases are 1.26 and 1.25 per the [Go release policy](https://go.dev/doc/devel/release#policy). Closing this 1.24 backport CL.
With the release of [Go 1.26.0](https://go.dev/doc/go1.26#introduction), the two latest supported major Go releases are 1.26 and 1.25 per the [Go release policy](https://go.dev/doc/devel/release#poli…
With the release of [Go 1.26.0](https://go.dev/doc/go1.26#introduction), the two latest supported major Go releases are 1.26 and 1.25 per the [Go release policy](https://go.dev/doc/devel/release#poli…
With the release of [Go 1.26.0](https://go.dev/doc/go1.26#introduction), the two latest supported major Go releases are 1.26 and 1.25 per the [Go release policy](https://go.dev/doc/devel/release#poli…
With the release of [Go 1.26.0](https://go.dev/doc/go1.26#introduction), the two latest supported major Go releases are 1.26 and 1.25 per the [Go release policy](https://go.dev/doc/devel/release#poli…
One of #63507 or #70090 can probably be closed as a duplicate of the other.
Note that https://github.com/golang/go/issues/63507#issuecomment-1759734314 includes motivation for the current behavior:
…
As of Go 1.25, the go command does not introduce the toolchain
directive on 'go get go@...' invocations if there wasn't already
a toolchain directive present. Relui didn't want to add those
directive…
The Go 1.26.0 release is out, so 1.25 is the oldest supported release.¹
The previous infrastructure (cmd/coordinator) does this automatically,
whereas here I authored this CL manually. We'll explore…
(1 comment)
If you want, this can be "Fixes" since it removes the draft notice, and doing that is the reason that issue [was left open](https://github.com/golang/go/issues/75005#issuecomment-3814390…
Still LGTM. Thanks again.
The newer links you've added are already using the works-in-more-contexts relative form, so consider applying that to this old link too.
```suggestion
Note that all user-v…
Does the same behavior reproduce if you try the example programs at [go-gl/example](https://github.com/go-gl/example)? If not, you can try bisecting between the two programs to narrow in on the cause…
(1 comment)
It's actually a minimal client for the k8s API, added back in 2015 (CL 14390). At some point I think it was used more heavily for k8s-based builders. By now I think our only remaining us…
In case it helps, noting here that I found breaking out a single analyzer run to happen first in the dashboard package is a viable workaround:
```sh
go fix -stringsseq ./dashboard # workaround for …
At this point, 'go fix ./...' produces zero diff and exit code 0.
The following CLs are follow ups to some of the earlier changes
that were generated. Their scope was intentionally to run a fix
as i…
The x/build repo has a good number of opportunities to modernize Go code, some older and some newer. In Go 1.26, [`go fix`](https://go.dev/doc/go1.26#go-command) is improved to make it much easier to…
Explain some of the subtle reasons for why runGo behaves as it does.
Do this to reduce chances of something accidentally breaking in the
future.
Based on suggestions Russ made in
https://go-review.g…
As of Go 1.23, the GOROOT_FINAL environment variable is no more¹,
and so it's no longer necessary to set it here. Start gradually
removing it.
Also, delete some code that became dead as of Go 1.24.…
The "log" field is documented as "the entire failed build log" at
https://go.dev/wiki/Watchflakes#records. In practice it was only
the top-level log text, and not the additional failures. Their logs
…
This is a continuation of issue #57050, to add missing documentation for a cmd/go behavior that's already implemented for a few more of its commands. ([CL 461683](https://go.dev/cl/461683) previously…
Thanks for offering to help.
I wouldn't describe its maintenance levels as very active, but I do still use it myself and ocassionally update it to include latest GitHub GraphQL schema changes. That'…
Thanks for the PR. I prefer to update go.mod and go.sum files separately.
I pushed commit 2402fdf4a9edcf51ed3f2eab4dc57c6867b10eea that includes schema changes by 2026-02-08. It doesn't yet includ…
Adding a note here that the exec format error on cipd_cache/bin/cipd is likely the same problem that was encountered in https://github.com/golang/go/issues/67306#issuecomment-3633590314. If so, you m…
Maintain the property that gopherbot doesn't enter a non-stop fighting
match with a human trying to reopen a cherry-pick issue, but still let
the submission of newer backport CLs re-close said issues…
[CL 553155](https://go.dev/cl/553155) reordered headings in the GitHub issue templates to be "got, want" (for issue #64890), but the issue template used by `go bug` still has the old inverse "want, g…
I agree that `go env -changed` cannot fully replace `go env`, but it can be a useful addition in many cases. Go's CI system prints all 3 of `go env`, `go env -changed`, and even `cmd/internal/metadat…
Thanks.
Needs a go mod tidy, I suspect.
I really can't tell which is less expensive: leaving this unresolved comment that gets in the way of this auto-submitting, or leaving it for a future CL at t…
Thanks very much.
Optional: maybe "new exported API" is better than "new API"; it doesn't add much verbosity but I think may help solidify that this isn't talking about internal API changes too.
> …
### Go version
go version go1.26rc3 darwin/arm64
### Output of `go env` in your module/workspace:
```shell
AR='ar'
CC='clang'
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_ENABLED=…
Hi @HeliC829, you recently sent a GitHub request to join the [golang/riscv64](https://github.com/orgs/golang/teams/riscv64) maintainer team. As suggested at https://go.dev/wiki/PortingPolicy#requirem…
Make some progress on removing log.Fatal calls from inner functions,
in favor of returning an error to the caller and doing log.Fatal in
main. This will help eventually retry more retryable errors wi…
The custom functionality to prepend an optional base URL to a target URL
implemented in BaseLink involves modifying the Path field. To avoid
disrupting what the EscapedPath method returns, it's neces…
Thanks.
So far we had a chance to try out the "nothing to upstream" path and that worked without uncovering anything new. We'll try the "1+ CL to upstream" path when it comes up next and adjust as n…
(2 comments)
The Go 1.25 blog post didn't link to https://go.dev/doc/go1.25#language because there weren't notable language changes, but I agree it's worth at least including a link to https://tip.g…
Thanks for considering this.
As mentioned in https://github.com/rsc/rf/issues/16#issuecomment-812623872, I think it's generally expected that tools working on packages in GOROOT need to use the co…
As I understand that PR applied the fix to the v4 major version of badger, but cas currently uses v3. That means either the badger fix needs to also be backported to its v3, and cas updated to that, …