(1 comment)
Is it expected that `go mod tidy` seemingly undoes this change (because the newly added requirements are only indirectly used)? This repo seems to use go-git/v5.
Patchset 3 passed all trybots, except go1.25-wasip1-wasm_wasmtime failed in time package due a timeout. It doesn't seem related, and it passed on second try, so adding bypass.
This looks related to issue #80484. It already has backport CLs in progress at [CL 812920](https://go.dev/cl/812920) and [CL 812920](https://go.dev/cl/812920), can you please check if those are enoug…
I'm not sure if retrying trybots will help. This passed on all trybots other than gotip-plan9-amd64 itself, but gotip-plan9-amd64 has a still-open known issue #63600 and it hasn't been green at https…
@Jorropo Are you referring to the fix in [CL 737880](https://go.dev/cl/737880) that was reverted (in [CL 794180](https://go.dev/cl/794180))? If so, that fix originally fixed issue #77153, and that is…
Thanks.
Do you know if having GOAMD64=v3 set in the environment will be enough and propagate to the rest of the perf tooling, without being cleared away for a consistent performance benchmarking sta…
Thanks.
Something to consider: a "release" team doesn't exist either, but we kept the GitHub team behind and repurposed it to be, as it's currently described:
> Members of this team are notified vi…
(2 comments)
This works, but given version.Compare exists, we could replace the entire versionLess helper with it.
So, please delete versionLess entirely, and in the places that currently use versi…
Thanks.
From a [quick search](https://cs.opensource.google/search?q=%22The%20Go%20Authors.%20%20All%20rights%20reserved.%22&sq=&ss=go), there may be a few more repos like x/arch, x/debug, x/perf tha…
Using too old of an x/tools version causes newer toolchains such as go1.27rc3 to run into errors like 'internal error: package "strings" without types was imported'. Updating to a newer x/tools versi…
This is already fixed for Go 1.28 by [CL 800700](https://go.dev/cl/800700), but it still happens on release branches.
@gopherbot Please consider this for backport. It's a small OpenBSD-only change t…
Thanks.
I find this description a little unclear since it doesn't say which bytes.
My current understanding is that the /connect-ssh HTTP handler first writes an HTTP response to the POST request, …
@rhysh made a suggestion to consider sending an email to golang-dev to notify Go developers at tip when the PRIVATE-track security fixes have finished landing. Adding a note here since this would be …
This issue is currently in the Unreleased milestone, meaning it's only associated with the golang.org/x/net module and not the main Go release cycle. Is it expected that the fix will be inside the x/…
> I'm surprised there isn't a failing test.
I suspect current test didn't catch a bad `pkgsiteCmdInternalDocVersion` constant value because it overrides the real pkgsite binary and its version with …
runtime:mayMoreStackMove.TestCoroLockOSThread/CoroLockOSThreadStopLockedIterNested failed on linux-arm64-longtest, otherwise everything passed. That failure is unrelated to this change.
By now PRIVATE-track security fixes involving a vendored package
have been released, and these tests can be made to run again.
For #80765.
For #80767.
[git-generate]
updatestd -goroot=$(pwd) -branc…
By now PRIVATE-track security fixes involving a vendored package
have been released, and these tests can be made to run again.
For #80744.
For #80745.
[git-generate]
updatestd -goroot=$(pwd) -branc…
Enforce a recursion limit in Unmarshal to prevent stack exhaustion when
parsing deeply-nested, recursive structures.
Thanks to Marwan Atia (marwansamir688@gmail.com) for reporting this
issue.
Fixes…
Closed by merging [CL 811000](https://go.dev/cl/811000) (commit cafd3448c7cb0b2d793bb4144d58f72ef3f48327) to release-branch.go1.25.
CC @golang/release, @mrkfrmn.
Closed by merging [CL 811000](https://go.dev/cl/811000) (commit cafd3448c7cb0b2d793bb4144d58f72ef3f48327) to release-branch.go1.25.
CC @golang/release, @mrkfrmn.
Closed by merging [CL 811020](https://go.dev/cl/811020) (commit 33ecb966ca47e55034272a9146e23e9909507f6d) to release-branch.go1.26.
CC @golang/release, @mrkfrmn.
Closed by merging [CL 811020](https://go.dev/cl/811020) (commit 33ecb966ca47e55034272a9146e23e9909507f6d) to release-branch.go1.26.
CC @golang/release, @mrkfrmn.
> I'm under the impression that to participate in the minors, this needs backports.
Indeed, all minor release fixes need a corresponding backport issue. In addition to tracking, the backport issues …
As far as I can tell, this wasn't intended to be added the Go1.26.5 milestone since it has no CherryPickCandidate label nor "[1.26 backport]" suffix in title, and it doesn't seem to fixed at tip yet.…
Thanks for the information. Since [CL 762500](https://go.dev/cl/762500) didn't have an issue associated, I filed #80850 for it retroactively and used it for the backport.
@gopherbot Please consider this for backport to Go 1.26. There's a semi-workaround available by using `CXXFLAGS` to control Fortran flags, but that can only be used if C++ flags aren't needed, and a …
https://pkg.go.dev/cmd/cgo#hdr-Using_cgo_with_the_go_command documents the behavior:
> CFLAGS, CPPFLAGS, CXXFLAGS, FFLAGS and LDFLAGS may be defined with pseudo #cgo directives within these comments…
Please see https://go.dev/wiki/MinorReleases for the backport process.
We'll need more information to consider a backport request, anything that would help us understand why a backport might be warr…
Thanks.
Consider requiring at least one builder that's running into this, e.g.:
```suggestion
Change-Id: I47aed66bc30fda86366042cbf8fcc32e6a6a6964
Cq-Include-Trybots: luci.golang.try:gotip-linux-am…
One of the remaining enhancements here is to re-check for any updates to the release notes when sending the announcement, so that it'd pick up any improvements to the release notes that may happen. (…
It was noted at https://groups.google.com/g/golang-dev/c/jMWTCiV0aSk/m/Qo6ozI0dBQAJ:
> Any CLs that land after CL 800721 ("internal/goversion: update Version to 1.28") but target go1.27.0 must be ch…
Thanks.
Thanks for checking. I asked because keeping these comments up to date will help with future maintenance of this sequence, and it seemed worth some extra attention.
This part seems out of d…