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?) -- 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/1be42173-6f3c-4840-854b-bf013edbb41en%40googlegroups.com.
