Skip to content

deps(gazelle): upgrade rules_go to remove patching of tree-sitter #3179

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 10 commits into
base: main
Choose a base branch
from

Conversation

jbedard
Copy link
Contributor

@jbedard jbedard commented Aug 14, 2025

Update rules_go to include bazel-contrib/rules_go#4298
Update gazelle to align with the version the rules_go bzlmod will bring in, and ensure the go.mod version is the same as bzlmod version.
Update go to 1.21 to include the slices library that some of the go.mod updates depend on.

Fixes #2956.

@jbedard jbedard force-pushed the stop-hacking-tree-sitter branch from f8b94b9 to 63a642a Compare August 15, 2025 00:00
Copy link
Collaborator

@dougthor42 dougthor42 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Odd... how did you avoid the windows issues with go-tree-sitter that I was seeing in #2962?

Ah well, I'm not going to look a gift horse in the mouth. This is awesome, thanks!

Requests:

  1. Update CHANGELOG.md to specify the version upgrades and that load statements might get reordered.
  2. Update MODULE.bazel's rules_go version to match what's used by gazelle/MODULE.bazel.
  3. Update internal_dev_deps.bzl to match too.
  4. Update examples/(bzlmod_)build_file_generation to match versions too.

@dougthor42 dougthor42 changed the title fix: upgrade rules_go to remove patching of tree-sitter deps(gazelle): upgrade rules_go to remove patching of tree-sitter Aug 15, 2025
@jbedard
Copy link
Contributor Author

jbedard commented Aug 15, 2025

Odd... how did you avoid the windows issues with go-tree-sitter that I was seeing in #2962?

I have no idea, don't jinx it! 😅

@jbedard jbedard requested a review from rickeylev as a code owner August 15, 2025 01:13
@jbedard
Copy link
Contributor Author

jbedard commented Aug 15, 2025

Now after upgrading things there's some odd failures. @dougthor42 can you take a look?

@jbedard jbedard requested a review from dougthor42 August 15, 2025 01:52
Copy link
Collaborator

@dougthor42 dougthor42 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To summarize all the comments:

  • You should be able to revert the .bazelignore and .bazelrc changes.
    • Doing so tested just fine for me locally, so 🤞.
  • You may be able to revert the change to root MODULE.bazel and WORKSPACE
    • Sorry for requesting those initially!
  • It seems like ae0f4be worked and just needs a CI retry.
  • Some nits

@jbedard jbedard force-pushed the stop-hacking-tree-sitter branch 2 times, most recently from ae0f4be to 353ec71 Compare August 15, 2025 05:05
@jbedard jbedard requested a review from dougthor42 August 15, 2025 05:25
@jbedard jbedard force-pushed the stop-hacking-tree-sitter branch from c4004be to 1ddc60b Compare August 15, 2025 05:34
Copy link
Collaborator

@dougthor42 dougthor42 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM; I'm just going to test it on our internal monorepo this morning to double check, but I don't expect any issues.

Copy link
Collaborator

@dougthor42 dougthor42 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I opened #3180 for the CI flake.

I'm just going to test it on our internal monorepo this morning to double check, but I don't expect any issues.

Things look good on my end. Approved.

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.

chore: update to rules_go v0.55.0
2 participants