Backward compatibility of "go mod vendor"?

93 views
Skip to first unread message

Davis Goodin

unread,
Sep 3, 2024, 1:58:50 PMSep 3
to golang-nuts
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?)

Ian Lance Taylor

unread,
Sep 3, 2024, 2:14:55 PMSep 3
to Davis Goodin, golang-nuts
This looks like a bug. Can you file it at https://go.dev/issue? Thanks.

Ian

Davis Goodin

unread,
Sep 3, 2024, 2:20:08 PMSep 3
to golang-nuts
Reply all
Reply to author
Forward
0 new messages