@fast-nail-55400 you think Go is "beta" rather than "alpha"? I think your third-party requirements improvement in 2.10 might mean yes. No change to the backend, only the language we use in docs.

I’d like to say yes but I’d first like to see a few non-trivial users using it without issue.

Yeah true. I think we're at least beta quality..the main existential issue I see is how to handle multiple go.mods do you think vendoring might make major changes to current functionality? As long as it's a new feature and not API change, that doesn't hurt stability

I have a (albeit rather trivial) go project I could try to Pantsify

That'd be great! Should be fairly trivial to set up: https://www.pantsbuild.org/v2.10/docs/go

do you think vendoring might make major changes to current functionality? As long as it’s a new feature and not API change, that doesn’t hurt stability

I don’t believe so. My initial thought there was to have

go_mod

generate a new

go_vendored_package

target type for vendored targets that references the in-tree vendored sources. (Name to be biked shedded.) Target generation would read the

vendor/modules.txt

under a

go.mod

to decide if a package was vendored or not.