Skip to content

Force update bazel-gazelle version#203

Draft
mateusz-olczyk wants to merge 6 commits into
mainfrom
issue-202/version-update
Draft

Force update bazel-gazelle version#203
mateusz-olczyk wants to merge 6 commits into
mainfrom
issue-202/version-update

Conversation

@mateusz-olczyk

Copy link
Copy Markdown
Collaborator

I need the latest fix from bazel-contrib/bazel-gazelle#2301 to resolve #202 correctly. Of course, the fix is not yet officially published in BCR, so I must use archive_override.

Signed-off-by: Mateusz Olczyk <molczyk@virtuslab.com>
Signed-off-by: Mateusz Olczyk <molczyk@virtuslab.com>
Signed-off-by: Mateusz Olczyk <molczyk@virtuslab.com>
Signed-off-by: Mateusz Olczyk <molczyk@virtuslab.com>
Signed-off-by: Mateusz Olczyk <molczyk@virtuslab.com>
Signed-off-by: Mateusz Olczyk <molczyk@virtuslab.com>
@mateusz-olczyk

Copy link
Copy Markdown
Collaborator Author

Something very weird happens with Bazel 9:

DEBUG: /Users/runner/Library/Caches/bazel/_bazel_runner/09db35e54e3333a54c5916ff31fffd16/external/gazelle+/internal/bzlmod/go_deps.bzl:629:40: 
Mismatch between versions requested for Go module github.com/bazelbuild/bazel-gazelle:

  bazel_dep version (MODULE.bazel): 0.46.0 (as "gazelle")
  Go module version (go.mod):       0.47.1-0.20260311181309-baca6fbbd606

It appears to completely ignore archive_override. It does not happen in the earlier Bazel versions. I have no idea what's wrong. It looks like a bug in Bazel 9.

Maybe we should just wait until the official bazel-gazelle version is released in BCR.

@mateusz-olczyk mateusz-olczyk marked this pull request as draft March 19, 2026 11:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Missing 'select' expression in case of only a single platform defined

1 participant