build: update bazel dependencies (main)#33503
Conversation
See associated pull request for more information.
There was a problem hiding this comment.
Code Review
This pull request updates rules_nodejs to version 6.7.5 and bazel_lib to version 3.4.0 in MODULE.bazel, along with corresponding updates in MODULE.bazel.lock. However, a critical issue was identified where the rules_nodejs module extension was completely removed from the lockfile, which will cause Bazel builds to fail in strict lockfile environments. To resolve this, the lockfile should be regenerated by running bazel mod tidy.
| ] | ||
| } | ||
| }, | ||
| "@@rules_nodejs+//nodejs:extensions.bzl%node": { |
There was a problem hiding this comment.
The rules_nodejs module extension (@@rules_nodejs+//nodejs:extensions.bzl%node) has been completely removed from the lockfile in this PR. Since this extension is actively used in MODULE.bazel (lines 40-61 and 63-129) to configure Node.js toolchains and export repositories, removing it will cause Bazel builds to fail in CI environments where strict lockfile checks are enforced (e.g., --lockfile_mode=error or --lockfile_mode=strict).
This often happens when dependency update bots (like Renovate) perform partial lockfile updates without fully evaluating all module extensions.
How to fix:
Please regenerate the lockfile locally by running:
bazel mod tidyor by running a dummy build to force extension evaluation:
bazel build --nobuild //...This will ensure that the node extension and its generated repository specs are correctly recorded in MODULE.bazel.lock.
This PR contains the following updates:
3.3.1→3.4.06.7.4→6.7.5Release Notes
bazel-contrib/rules_nodejs (rules_nodejs)
v6.7.5Using Bzlmod with Bazel 6 or greater
common --enable_bzlmodin.bazelrc.MODULE.bazelfile:Using WORKSPACE
Paste this snippet into your
WORKSPACE.bazelfile:What's Changed
Full Changelog: bazel-contrib/rules_nodejs@v6.7.4...v6.7.5