golang-dev

From the convention that I see being followed, it should be a +2 with a wait-release hashtag. On

Hi Cherry, Thanks for the update Regards Dimas On Fri, Mar 21, 2025 at 9:12 PM Cherry Mui <cherry@

I see thx, about 72866 I've asked the original reporter to reply on the issue. And another thing

The buggy code has never been merged nor submitted, nothing to fix. Le mar. 11 mars 2025, 01:04, Russ

Hi all, Starting around December 16, some (but not all) posts to golang-dev got replies sent back to

Thanks On Fri, 7 Mar 2025, 6:05 pm 'ame...@google.com' via golang-dev, <golang-dev@

>Inliner related #72090, #72063 and #71680 strikes me as being the "same" bug, All these

Hello gophers, We have just released Go versions 1.24.1 and 1.23.7, minor point releases. These minor

Thank you for your insight, Ian. I will explore the "Suggested" issues to learn about their

Hello gophers, We plan to issue a security fix for the packages golang.org/x/net/proxy and golang.org

Hello gophers, We plan to issue Go 1.24.1 and Go 1.23.7 during US business hours on Tuesday, March 4.

Thanks, we are already using pqclean implementations, but were looking for a production ready native

Hello gophers, We have tagged version v0.27.0 of golang.org/x/oauth2 in order to address a security

Hello gophers, We plan to issue a security fix for the package golang.org/x/crypto/ssh in the golang.

Hello gophers, We plan to issue a security fix for the package golang.org/x/oauth2/jws in the golang.

Hello gophers, We have just released Go 1.24.0. To find out what has changed in Go 1.24, read the

Provoked by the bolt-go malicious package cache exploit last week, I've been thinking about how

Hello gophers, We have just released go1.24rc3, a release candidate version of Go 1.24. This release

Hello gophers, We have just released Go versions 1.23.6 and 1.22.12, minor point releases. These

Hi Gophers, The tree is now open for general development of Go 1.25. It will remain open until the

Hello gophers, We plan to issue Go 1.24 RC3 during US business hours on Wednesday, February 5. The Go

I believe it's equivalent to this declined proposal: https://go.dev/issue/42847 proposal: Go 2:

Hello, In my CI, with 1.24rc2 I have this report below. From my point of view, this CVE is only for

Hello! Our next Go core (compiler/runtime & Go releases) office hours will be held on February 6

Hello! I would like use go.dev (make requests with go code) in my project, it's open-source and

Hello Gophers, We are about 3 weeks from the Go 1.24.0 release. At this time in the Go1.24 milestone,

As stated on the playground about page, > Any requests for content removal should be directed to

Hello gophers, We have just released Go versions 1.23.5 and 1.22.11, minor point releases. These

Hi, I'm writing with regard to a note from the Go blog post at https://go.dev/blog/playground#

Hello gophers, We plan to issue Go 1.23.5, Go 1.22.11, and Go 1.24 RC2 during US business hours on

Somebody once told me not to ask for change too fast, and that was good advice. We haven't