Done, thanks: cmd/go: running `go1.23.0 mod vendor` on go1.22.6 source unexpectedly vendors `golang.org/x/crypto/sha3` · Issue #69235 · golang/go (github.com) <https://github.com/golang/go/issues/69235>
On Tuesday, September 3, 2024 at 11:14:55 AM UTC-7 Ian Lance Taylor wrote: > On Tue, Sep 3, 2024 at 10:59 AM 'Davis Goodin' via golang-nuts > <golan...@googlegroups.com> wrote: > > > > I noticed today that taking the Go 1.22.6 source tree and running > "go1.22.6 mod vendor" and "go1.23.0 mod vendor" give me different results. > (Vendoring using go1.23.0 adds golang.org/x/crypto/sha3.) > > > > I've been working under the assumption that backward compatibility > promises would extend to "go mod vendor". This way, developers using 1.23.x > and 1.22.x won't have thrashing changes when working on the same module. > > > > Did I pick up a bad assumption? Or is this a bug? > > > > (Or is the standard library module special?) > > This looks like a bug. Can you file it at https://go.dev/issue? Thanks. > > Ian > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/cb277a2e-a7b4-423c-97b5-aa06c168d6b8n%40googlegroups.com.
