From 9dbb5e6653a2b9d80ef68e781154c6f5f0f592bc Mon Sep 17 00:00:00 2001 From: Joshua Yanchar Date: Wed, 29 Jul 2026 02:59:52 -0700 Subject: [PATCH] docs(bazel): stop pinning a Go patch version in the gazelle_python note MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The TEND(tooling) comment named "our Go 1.26.4 SDK", which Renovate's 1.26.4 -> 1.26.5 bump (#210) left stale — it moved the go_sdk.download pins but not the prose. The patch version was never load-bearing: upstream bazel-contrib/rules_python#3416 frames the smacker/go-tree-sitter breakage as a cgo cross-compilation problem (Windows/Darwin), not a regression at some Go release, so the comment now refers to the pinned SDK without naming it. --- MODULE.bazel | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/MODULE.bazel b/MODULE.bazel index d6ad351..8f7cec8 100644 --- a/MODULE.bazel +++ b/MODULE.bazel @@ -96,7 +96,7 @@ use_repo(pip, "unnatural_designs_pypi") # TEND(tooling): rules_python_gazelle_plugin (a.k.a. gazelle_python) is not wired # here. The plugin's gazelle binary pulls in smacker/go-tree-sitter via CGO, -# which does not compile under our Go 1.26.4 SDK (upstream issue +# which does not compile under our pinned Go SDK (upstream issue # bazel-contrib/rules_python#3416; the migration to a pure-Go binding is in # the unmerged bazel-contrib/rules_python#3786). Until #3786 ships in a # release, Python BUILD files are hand-authored. See