Skip to content
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

chore: upgrade to Bazel 7.1.1 #3728

Merged
merged 1 commit into from
Apr 2, 2024
Merged

chore: upgrade to Bazel 7.1.1 #3728

merged 1 commit into from
Apr 2, 2024

Conversation

gregmagolan
Copy link
Collaborator

@gregmagolan gregmagolan commented Apr 2, 2024

Fixes up the e2e/smoke bzlmod test as well. The default Node.js version of 18 breaks on Bazel CI due to GLIBC incompatibility with the runner so default Node.js must be < 18.

@gregmagolan gregmagolan force-pushed the bump_bazel_version branch 3 times, most recently from 9ed8cc8 to 64e2c31 Compare April 2, 2024 05:18
# Note, this gets the default version of Node.js from
# https://github.com/bazelbuild/rules_nodejs/blob/5.8.0/nodejs/repositories.bzl#L11
node.toolchain(
name = "node16",
Copy link
Collaborator

Choose a reason for hiding this comment

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

Why drop this when upgrading bazel?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

I mentioned it in the PR summary. Getting to bazel means the bzlmod by default and that means the default toolchain is used which is Node 18. Node 18 doesn't run on the Bazel CI runners because it requires a newer version of GLIBC.

Copy link
Collaborator

Choose a reason for hiding this comment

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

The PR summary says nothing about the toolchain name. Why change the name making the diff 10x larger?

@gregmagolan gregmagolan merged commit 9945b4f into main Apr 2, 2024
4 checks passed
@gregmagolan gregmagolan deleted the bump_bazel_version branch April 2, 2024 13:36
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.

3 participants