Gazelle cannot parse new go.mod directives

[uhthomas]

What version of gazelle are you using?

v0.37.0

What version of rules_go are you using?

v0.48.0

What version of Bazel are you using?

6.5.0

Does this issue reproduce with the latest releases of all the above?

Yes.

What operating system and processor architecture are you using?

Linux x86

What did you do?

bazel run //:gazelle

go 1.22.2

toolchain go1.22.3

What did you expect to see?

What did you see instead?

gazelle: reading module paths from /home/thomas/code/github.com/uhthomas/automata/go.mod: /home/thomas/code/gith
ub.com/uhthomas/automata/go.mod:3: invalid go version '1.22.2': must match format 1.23
/home/thomas/code/github.com/uhthomas/automata/go.mod:5: unknown directive: toolchain

[fmeum]

The go_deps extension with Bzlmod has support for this directive already. Is it possible for you to migrate? Happy to review a PR as well.

[uhthomas]

The go_deps extension with Bzlmod has support for this directive already. Is it possible for you to migrate? Happy to review a PR as well.

I see - I'm still using rules_k8s and rules_docker. I guess I'd need to figure out how to replace them.

[fmeum]

Do they straight up don't work with Bzlmod? You should generally be able to keep them in WORKSPACE or WORKSPACE.bzlmod and just migrate the rest.

[uhthomas]

Do they straight up don't work with Bzlmod? You should generally be able to keep them in WORKSPACE or WORKSPACE.bzlmod and just migrate the rest.

I remember trying this on a different repository and it went horribly. Has the situation improved?

[fmeum]

I unfortunately don't know, I don't use them myself.